Device, method, and graphical user interface for navigating user interface hierarchies

ABSTRACT

An electronic device with a touch-sensitive surface, a display, and one or more sensors to detect intensity of contacts displaying a lower-level user interface that is part of a user interface hierarchy, where the hierarchy includes at least three levels, including the lower-level user interface, an intermediate-level user interface and a higher-level user interface. The device also, while displaying the lower-level user interface, detects an input on a portion of the device that is associated with user interface hierarchy navigation and, in response to detecting the input, in accordance with a determination that the input meets first transition criteria, the device replaces display of the lower-level user interface with display of the intermediate-level user interface and in accordance with a determination that the input meets second transition criteria, the device replaces display of the lower-level user interface with display of the higher-level user interface.

RELATED APPLICATIONS

This application is a continuation of PCT Patent Application Serial No.PCT/US2013/069472, filed on Nov. 11, 2013, entitled “Device, Method, andGraphical User Interface for Navigating User Interface Hierarchies,”which claims the benefit of and priority to U.S. Provisional PatentApplication Ser. No. 61/778,125, filed on Mar. 12, 2013, entitled“Device, Method, and Graphical User Interface for Navigating UserInterface Hierarchies;” and U.S. Provisional Patent Application No.61/747,278, filed Dec. 29, 2012, entitled “Device, Method, and GraphicalUser Interface for Manipulating User Interface Objects with Visualand/or Haptic Feedback,” which applications are incorporated byreference herein in their entireties.

This application is also related to the following: U.S. ProvisionalPatent Application Ser. No. 61/778,092, filed on Mar. 12, 2013, entitled“Device, Method, and Graphical User Interface for Selecting Objectwithin a Group of Objects;” U.S. Provisional Patent Application Ser. No.61/778,156, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Manipulating Framed Graphical Objects;”U.S. Provisional Patent Application Ser. No. 61/778,179, filed on Mar.12, 2013, entitled “Device, Method, and Graphical User Interface forScrolling Nested Regions;” U.S. Provisional Patent Application Ser. No.61/778,171, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Displaying Additional Information inResponse to a User Contact;” U.S. Provisional Patent Application Ser.No. 61/778,191, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application;” U.S. Provisional Patent ApplicationSer. No. 61/778,211, filed on Mar. 12, 2013, entitled “Device, Method,and Graphical User Interface for Facilitating User Interaction withControls in a User Interface;” U.S. Provisional Patent Application Ser.No. 61/778,239, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Forgoing Generation of Tactile Output for aMulti-Contact Gesture;” U.S. Provisional Patent Application Ser. No.61/778,284, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Providing Tactile Feedback for OperationsPerformed in a User Interface;” U.S. Provisional Patent Application Ser.No. 61/778,287, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Providing Feedback for Changing ActivationStates of a User Interface Object;” U.S. Provisional Patent ApplicationSer. No. 61/778,363, filed on Mar. 12, 2013, entitled “Device, Method,and Graphical User Interface for Transitioning between Touch Input toDisplay Output Relationships;” U.S. Provisional Patent Application Ser.No. 61/778,367, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Moving a User Interface Object Based on anIntensity of a Press Input;” U.S. Provisional Patent Application Ser.No. 61/778,265, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Transitioning between Display States inResponse to a Gesture;” U.S. Provisional Patent Application Ser. No.61/778,373, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Managing Activation of a Control Based onContact Intensity;” U.S. Provisional Patent Application Ser. No.61/778,412, filed on Mar. 13, 2013, entitled “Device, Method, andGraphical User Interface for Displaying Content Associated with aCorresponding Affordance;” U.S. Provisional Patent Application Ser. No.61/778,413, filed on Mar. 13, 2013, entitled “Device, Method, andGraphical User Interface for Selecting User Interface Objects;” U.S.Provisional Patent Application Ser. No. 61/778,414, filed on Mar. 13,2013, entitled “Device, Method, and Graphical User Interface for Movingand Dropping a User Interface Object;” U.S. Provisional PatentApplication Ser. No. 61/778,416, filed on Mar. 13, 2013, entitled“Device, Method, and Graphical User Interface for Determining Whether toScroll or Select Content;” and U.S. Provisional Patent Application Ser.No. 61/778,418, filed on Mar. 13, 2013, entitled “Device, Method, andGraphical User Interface for Switching between User Interfaces,” whichare incorporated herein by reference in their entireties.

This application is also related to the following: U.S. ProvisionalPatent Application Ser. No. 61/645,033, filed on May 9, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. ProvisionalPatent Application Ser. No. 61/665,603, filed on Jun. 28, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” and U.S. ProvisionalPatent Application Ser. No. 61/681,098, filed on Aug. 8, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices,” which areincorporated herein by reference in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that detect inputs for manipulating userinterfaces.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touch pads and touchscreen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Exemplary manipulations include adjusting the position and/or size ofone or more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Exemplary user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture or iPhoto from AppleInc. of Cupertino, Calif.), a digital content (e.g., videos and music)management application (e.g., iTunes from Apple Inc. of Cupertino,Calif.), a drawing application, a presentation application (e.g.,Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But existing methods for performing these manipulations are cumbersomeand inefficient. In addition, existing methods take longer thannecessary, thereby wasting energy. This latter consideration isparticularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for manipulating user interfaces. Suchmethods and interfaces optionally complement or replace conventionalmethods for manipulating user interfaces. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated devices, such methods andinterfaces conserve power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, website creating, disk authoring, spreadsheet making, gameplaying, telephoning, video conferencing, e-mailing, instant messaging,workout support, digital photographing, digital videoing, web browsing,digital music playing, and/or digital video playing. Executableinstructions for performing these functions are, optionally, included ina non-transitory computer readable storage medium or other computerprogram product configured for execution by one or more processors.

There is a need for electronic devices with faster, more efficientmethods and interfaces for navigating user interface hierarchies. Suchmethods and interfaces may complement or replace conventional methodsfor navigating user interface hierarchies. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated devices, such methods andinterfaces conserve power and increase the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes displaying, on the display, a lower-leveluser interface that is part of a user interface hierarchy, where: thehierarchy includes at least three levels, including the lower-level userinterface, an intermediate-level user interface and a higher-level userinterface; the intermediate-level user interface is above thelower-level user interface in the hierarchy; and the higher-level userinterface is above both the intermediate-level user interface and thelower-level user interface in the hierarchy. The method furtherincludes, while displaying the lower-level user interface, detecting aninput on a portion of the device that is associated with user interfacehierarchy navigation, and in response to detecting the input, inaccordance with a determination that the input meets first transitioncriteria that include a criterion that a maximum intensity of the inputis above a first intensity threshold and below a second intensitythreshold, where the second intensity threshold is higher than the firstintensity threshold, replacing display of the lower-level user interfacewith display of the intermediate-level user interface, and in accordancewith a determination that the input meets second transition criteriathat include a criterion that a maximum intensity of the input is abovethe second intensity threshold, replacing display of the lower-leveluser interface with display of the higher-level user interface.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a lower-level user interface that ispart of a user interface hierarchy, where: the hierarchy includes atleast three levels, including the lower-level user interface, anintermediate-level user interface and a higher-level user interface; theintermediate-level user interface is above the lower-level userinterface in the hierarchy; and the higher-level user interface is aboveboth the intermediate-level user interface and the lower-level userinterface in the hierarchy, a touch-sensitive surface unit configured toreceive user inputs, one or more sensor units configured to detectintensity of contacts with the touch-sensitive surface unit, and aprocessing unit coupled to the display unit, the touch-sensitive surfaceunit, and the sensor units. The processing unit is configured to, whiledisplaying the lower-level user interface, detect an input on a portionof the device that is associated with user interface hierarchynavigation, and in response to detecting the input, in accordance with adetermination that the input meets first transition criteria thatinclude a criterion that a maximum intensity of the input is above afirst intensity threshold and below a second intensity threshold, wherethe second intensity threshold is higher than the first intensitythreshold, replace display of the lower-level user interface withdisplay of the intermediate-level user interface, and in accordance witha determination that the input meets second transition criteria thatinclude a criterion that a maximum intensity of the input is above thesecond intensity threshold, replace display of the lower-level userinterface with display of the higher-level user interface.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor navigating user interface hierarchies, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventional methodsfor navigating user interface hierarchies.

There is a need for electronic devices with faster, more efficientmethods and interfaces for navigating user interface hierarchies. Suchmethods and interfaces may complement or replace conventional methodsfor navigating user interface hierarchies. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated devices, such methods andinterfaces conserve power and increase the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes displaying, on the display, a lower-leveluser interface that is part of a user interface hierarchy, where: thehierarchy includes at least three levels, including the lower-level userinterface, an intermediate-level user interface and a higher-level userinterface; the intermediate-level user interface is above thelower-level user interface in the hierarchy; and the higher-level userinterface is above both the intermediate-level user interface and thelower-level user interface in the hierarchy. The method furtherincludes, while displaying the lower-level user interface, detecting aninput on a portion of the device that is associated with user interfacehierarchy navigation and, in response to detecting the input, inaccordance with a determination that the input has a duration shorterthan a respective time threshold, replacing display of the lower-leveluser interface with display of the higher-level user interface, and inaccordance with a determination that the input has a duration longerthan the respective time threshold, replacing display of the lower-leveluser interface with display of a respective user interface in the userinterface hierarchy selected in accordance with an intensity of theinput.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a lower-level user interface that ispart of a user interface hierarchy, where: the hierarchy includes atleast three levels, including the lower-level user interface, anintermediate-level user interface and a higher-level user interface; theintermediate-level user interface is above the lower-level userinterface in the hierarchy; and the higher-level user interface is aboveboth the intermediate-level user interface and the lower-level userinterface in the hierarchy, a touch-sensitive surface unit configured toreceive user inputs, one or more sensor units configured to detectintensity of contacts with the touch-sensitive surface unit, and aprocessing unit coupled to the display unit, the touch-sensitive surfaceunit, and the sensor units. The processing unit is configured to, whiledisplaying the lower-level user interface, detect an input on a portionof the device that is associated with user interface hierarchynavigation, and in response to detecting the input, in accordance with adetermination that the input has a duration shorter than a respectivetime threshold, replace display of the lower-level user interface withdisplay of the higher-level user interface, and in accordance with adetermination that the input has a duration longer than the respectivetime threshold, replace display of the lower-level user interface withdisplay of a respective user interface in the user interface hierarchyselected in accordance with an intensity of the input.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor navigating user interface hierarchies, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventional methodsfor navigating user interface hierarchies.

There is a need for electronic devices with faster, more efficientmethods and interfaces for gradually displaying a respective userinterface on a display. Such methods and interfaces may complement orreplace conventional methods for gradually displaying a respective userinterface. Such methods and interfaces reduce the cognitive burden on auser and produce a more efficient human-machine interface. Forbattery-operated devices, such methods and interfaces conserve power andincrease the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: while the display is in a low-power mode,detecting an input on the touch-sensitive surface, where detecting theinput includes detecting a contact on the touch-sensitive surface anddetecting a change in a characteristic of the contact. The methodfurther includes: in response to detecting the input, in accordance witha determination that the input meets display-activation criteria,gradually displaying a respective user interface on the display inaccordance with the change in the characteristic of the contact, wherethe respective user interface was not displayed on the display when thedisplay was in the low-power mode.

In accordance with some embodiments, an electronic device includes adisplay unit configured display information; a touch-sensitive surfaceunit configured to receive contacts; one or more sensors unitsconfigured to detect intensity of contacts with the touch-sensitivesurface unit; and a processing unit coupled to the display unit, thetouch-sensitive surface unit, and the one or more sensor units. Theprocessing unit is configured to: while the display unit is in alow-power mode, detect an input on the touch-sensitive surface unit,where detecting the input includes detecting a contact on thetouch-sensitive surface unit and detecting a change in a characteristicof the contact. The processing unit it further configured to: inresponse to detecting the input and in accordance with a determinationthat the input meets display-activation criteria, gradually display arespective user interface on the display unit in accordance with thechange in the characteristic of the contact, where the respective userinterface was not displayed on the display unit when the display unitwas in the low-power mode.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor gradually displaying a respective user interface on a display, forexample while transitioning from a low-power mode, thereby increasingthe effectiveness, efficiency, and user satisfaction with such devices.Such methods and interfaces may complement or replace conventionalmethods for gradually displaying a respective user interface.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensity of contacts with the touch-sensitive surface, one ormore processors, memory, and one or more programs; the one or moreprograms are stored in the memory and configured to be executed by theone or more processors and the one or more programs include instructionsfor performing the operations of any of the methods referred to in thefifth paragraph of the Description of Embodiments. In accordance withsome embodiments, a graphical user interface on an electronic devicewith a display, a touch-sensitive surface, optionally one or moresensors to detect intensity of contacts with the touch-sensitivesurface, a memory, and one or more processors to execute one or moreprograms stored in the memory includes one or more of the elementsdisplayed in any of the methods referred to in the fifth paragraph ofthe Description of Embodiments, which are updated in response to inputs,as described in any of the methods referred to in the fifth paragraph ofthe Description of Embodiments. In accordance with some embodiments, acomputer readable storage medium has stored therein instructions whichwhen executed by an electronic device with a display, a touch-sensitivesurface, and optionally one or more sensors to detect intensity ofcontacts with the touch-sensitive surface, cause the device to performthe operations of any of the methods referred to in the fifth paragraphof the Description of Embodiments. In accordance with some embodiments,an electronic device includes: a display, a touch-sensitive surface, andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface; and means for performing the operations of anyof the methods referred to in the fifth paragraph of the Description ofEmbodiments. In accordance with some embodiments, an informationprocessing apparatus, for use in an electronic device with a display anda touch-sensitive surface, optionally one or more sensors to detectintensity of contacts with the touch-sensitive surface, includes meansfor performing the operations of any of the methods referred to in thefifth paragraph of the Description of Embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 5A-5U illustrate exemplary user interfaces navigating userinterface hierarchies in accordance with some embodiments.

FIGS. 6A-6D are flow diagrams illustrating a method of navigating userinterface hierarchies in accordance with some embodiments.

FIG. 7 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 8A-8V illustrate exemplary user interfaces for navigating userinterface hierarchies in accordance with some embodiments.

FIGS. 9A-9E are flow diagrams illustrating a method of navigating userinterface hierarchies in accordance with some embodiments.

FIG. 10 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 11A-11U illustrate exemplary user interfaces for graduallydisplaying a respective user interface on a display in accordance withsome embodiments.

FIGS. 12A-12D are flow diagrams illustrating a method of graduallydisplaying a respective user interface on a display in accordance withsome embodiments.

FIG. 13 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The methods, devices and GUIs described herein provide visual and/orhaptic feedback that makes manipulation of user interface objects moreefficient and intuitive for a user. For example, in a system where theclicking action of a trackpad is decoupled from the contact intensity(e.g., contact force, contact pressure, or a substitute therefore) thatis needed to reach an activation threshold, the device can generatedifferent tactile outputs (e.g., “different clicks”) for differentactivation events (e.g., so that clicks that accomplish a particularresult are differentiated from clicks that do not produce any result orthat accomplish a different result from the particular result).Additionally, tactile outputs can be generated in response to otherevents that are not related to increasing intensity of a contact, suchas generating a tactile output (e.g., a “detent”) when a user interfaceobject is moved to a particular position, boundary or orientation, orwhen an event occurs at the device.

Additionally, in a system where a trackpad or touch-screen display issensitive to a range of contact intensity that includes more than one ortwo specific intensity values (e.g., more than a simple on/off, binaryintensity determination), the user interface can provide responses(e.g., visual or tactile cues) that are indicative of the intensity ofthe contact within the range. In some implementations, apre-activation-threshold response and/or a post-activation-thresholdresponse to an input are displayed as continuous animations. As oneexample of such a response, a preview of an operation is displayed inresponse to detecting an increase in contact intensity that is stillbelow an activation threshold for performing the operation. As anotherexample of such a response, an animation associated with an operationcontinues even after the activation threshold for the operation has beenreached. Both of these examples provide a user with a continuousresponse to the force or pressure of a user's contact, which provides auser with visual and/or haptic feedback that is richer and moreintuitive. More specifically, such continuous force responses give theuser the experience of being able to press lightly to preview anoperation and/or press deeply to push “past” or “through” a predefineduser interface state corresponding to the operation.

Additionally, for a device with a touch-sensitive surface that issensitive to a range of contact intensity, multiple contact intensitythresholds can be monitored by the device and different functions can bemapped to different contact intensity thresholds. This serves toincrease the available “gesture space” providing easy access to advancedfeatures for users who know that increasing the intensity of a contactat or beyond a second “deep press” intensity threshold will cause thedevice to perform a different operation from an operation that would beperformed if the intensity of the contact is between a first“activation” intensity threshold and the second “deep press” intensitythreshold. An advantage of assigning additional functionality to asecond “deep press” intensity threshold while maintaining familiarfunctionality at a first “activation” intensity threshold is thatinexperienced users who are, in some circumstances, confused by theadditional functionality can use the familiar functionality by justapplying an intensity up to the first “activation” intensity threshold,whereas more experienced users can take advantage of the additionalfunctionality by applying an intensity at the second “deep press”intensity threshold.

Additionally, for a device with a touch-sensitive surface that issensitive to a range of contact intensity, the device can provideadditional functionality by allowing users to perform complex operationswith a single continuous contact. For example, when selecting a group ofobjects, a user can move a continuous contact around the touch-sensitivesurface and can press while dragging (e.g., applying an intensitygreater than a “deep press” intensity threshold) to add additionalelements to a selection. In this way, a user can intuitively interactwith a user interface where pressing harder with a contact causesobjects in the user interface to be “stickier.”

A number of different approaches to providing an intuitive userinterface on a device where a clicking action is decoupled from theforce that is needed to reach an activation threshold and/or the deviceis sensitive to a wide range of contact intensities are described below.Using one or more of these approaches (optionally in conjunction witheach other) helps to provide a user interface that intuitively providesusers with additional information and functionality, thereby reducingthe user's cognitive burden and improving the human-machine interface.Such improvements in the human-machine interface enable users to use thedevice faster and more efficiently. For battery-operated devices, theseimprovements conserve power and increase the time between batterycharges. For ease of explanation, systems, methods and user interfacesfor including illustrative examples of some of these approaches aredescribed below, as follows:

-   -   Many electronic devices have graphical user interfaces that        include various user interface hierarchies and it is easy for a        user to lose their place within the user interface hierarchy or        become confused as to how to navigate through the user interface        hierarchy. The embodiments described below improve on these        methods by reducing the cognitive burden on a user and produce        an intuitive and efficient human-machine interface by navigating        through a user interface hierarchy in accordance with an        intensity of a detected input and providing visual feedback        indicative of the navigation through the user interface        hierarchy. In particular, FIGS. 5A-5U illustrate exemplary user        interfaces for navigating a user interface hierarchy using        inputs on a touch-sensitive surface. FIGS. 6A-6D are flow        diagrams illustrating a method of navigating a user interface        hierarchy using inputs on a touch-sensitive surface. The user        interfaces in FIGS. 5A-5U are further used to illustrate the        processes described below with reference to FIGS. 6A-6D.    -   Many electronic devices have graphical user interfaces that        include various user interface hierarchies and it is easy for a        user to lose their place within the user interface hierarchy or        become confused as to how to navigate through the user interface        hierarchy. The embodiments below improve on these methods by        reducing the cognitive burden on a user and produce a more        intuitive and efficient human-machine interface by determining,        based on a duration of a detected input, whether to navigate        through a user interface hierarchy in accordance with an        intensity of the detected input and provide visual feedback        indicative of the navigation through the user interface        hierarchy or to navigate through the user interface hierarchy        using different feedback. FIGS. 8A-8V illustrate exemplary user        interfaces for navigating a user interface hierarchy using        inputs on a touch-sensitive surface. FIGS. 9A-9E are flow        diagrams illustrating a method of navigating a user interface        hierarchy using inputs on a touch-sensitive surface. The user        interfaces in FIGS. 8A-8V are further used to illustrate the        processes described below with reference to FIGS. 9A-9E.    -   Many electronic devices display a graphical user interface on a        display in response to a user action (e.g., moving a mouse or        pressing a power button) subsequent to the display being in a        low-power state (e.g., sleep mode or an off state) where the        graphical user interface is not displayed on the display.        However the transition between the low-power state and        displaying the graphical user interface can be jarring to the        user and/or unnecessarily consume power of the device when the        user does not want the transition the device out of the        low-power state. The embodiments described below improve on        these methods by gradually displaying the graphical user        interface in response to detecting a change in a characteristic        of the contact (e.g., an increase in intensity of the contact)        while a display of the device is in a low-power mode. Gradually        displaying the graphical user interface in response to detecting        the change in the characteristic of the contact provides an        efficient and intuitive user interface that reduces the        cognitive burden on the user and enables the user to cancel        display of the graphical user interface if the user does not        want to transition the device out of the low-power state after        viewing the first portion of the gradual display of the user        interface. FIGS. 11A-11U illustrate exemplary user interfaces        for gradually displaying a respective user interface on a        display. FIGS. 12A-12D are flow diagrams illustrating a method        of gradually displaying a respective user interface on a        display. The user interfaces in FIGS. 11A-11U are used to        illustrate the processes in FIGS. 12A-12D.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touch pad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPU's) 120, peripherals interface 118, RF circuitry 108, audiocircuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem106, other input or control devices 116, and external port 124. Device100 optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on the touchsensitive surface, or to a substitute (proxy) for the force or pressureof a contact on the touch sensitive surface. The intensity of a contacthas a range of values that includes at least four distinct values andmore typically includes hundreds of distinct values (e.g., at least256). Intensity of a contact is, optionally, determined (or measured)using various approaches and various sensors or combinations of sensors.For example, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU 120 and the peripherals interface118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), Instant Messaging and Presence Service(IMPS)), and/or Short Message Service (SMS), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 optionally capturesstill images or video. In some embodiments, an optical sensor is locatedon the back of device 100, opposite touch screen display 112 on thefront of the device, so that the touch screen display is enabled for useas a viewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained forvideoconferencing while the user views the other video conferenceparticipants on the touch screen display.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is coupled to input controller 160 inI/O subsystem 106. In some embodiments, the proximity sensor turns offand disables touch screen 112 when the multifunction device is placednear the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112 which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact) determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns and intensities. Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 are, optionally, used to manage an address book or contactlist (e.g., stored in application internal state 192 of contacts module137 in memory 102 or memory 370), including: adding name(s) to theaddress book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 are, optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in address book 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in a MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 are,optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 are,optionally, used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward)and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that is, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Text;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online Video”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Map;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments the touch sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementationsfocus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

The user interface figures described below include various intensitydiagrams that show the current intensity of the contact on thetouch-sensitive surface relative to one or more intensity thresholds(e.g., a contact detection intensity threshold IT₀, a light pressintensity threshold IT_(L), a deep press intensity threshold IT_(D),and/or one or more other intensity thresholds). This intensity diagramis typically not part of the displayed user interface, but is providedto aid in the interpretation of the figures. In some embodiments, thelight press intensity threshold corresponds to an intensity at which thedevice will perform operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, the deeppress intensity threshold corresponds to an intensity at which thedevice will perform operations that are different from operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, when a contact is detected with anintensity below the light press intensity threshold (e.g., and above anominal contact-detection intensity threshold IT₀ below which thecontact is no longer detected), the device will move a focus selector inaccordance with movement of the contact on the touch-sensitive surfacewithout performing an operation associated with the light pressintensity threshold or the deep press intensity threshold. Generally,unless otherwise stated, these intensity thresholds are consistentbetween different sets of user interface figures.

An increase of intensity of the contact from an intensity below thelight press intensity threshold IT_(L) to an intensity between the lightpress intensity threshold IT_(L) and the deep press intensity thresholdIT_(D) is sometimes referred to as a “light press” input. An increase ofintensity of the contact from an intensity below the deep pressintensity threshold IT_(D) to an intensity above the deep pressintensity threshold IT_(D) is sometimes referred to as a “deep press”input. An increase of intensity of the contact from an intensity belowthe contact-detection intensity threshold IT₀ to an intensity betweenthe contact-detection intensity threshold IT₀ and the light pressintensity threshold IT_(L) is sometimes referred to as detecting thecontact on the touch-surface. A decrease of intensity of the contactfrom an intensity above the contact-detection intensity threshold IT₀ toan intensity below the contact intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments IT₀ is greater thanzero. In some illustrations a shaded circle or oval is used to representintensity of a contact on the touch-sensitive surface. In someillustrations a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90% or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

User Interfaces and Associated Processes Navigating User InterfaceHierarchies

Many electronic devices have graphical user interfaces that includevarious user interface hierarchies and it is easy for a user to losetheir place within the user interface hierarchy or become confused as tohow to navigate through the user interface hierarchy. For example, amedia player application includes several interfaces for users tonavigate between. In this example, the media player application's userinterface hierarchy includes a media presentation interface, a mediacollection display interface, and a user interface with an applicationlaunch icon for the media player application (e.g., a home or startinginterface). The embodiments below improve on these methods by reducingthe cognitive burden on a user and produce an intuitive and efficienthuman-machine interface by navigating through a user interface hierarchyin accordance with an intensity of a detected input and providing visualfeedback indicative of the navigation through the user interfacehierarchy.

FIGS. 5A-5U illustrate exemplary user interfaces for navigating a userinterface hierarchy using inputs on a touch-sensitive surface inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses described below with reference to FIGS. 6A-6D. FIGS. 5C-5Pinclude intensity diagrams that show the current intensity of thecontact on the touch-sensitive surface relative to a plurality ofintensity thresholds including a contact detection intensity threshold(e.g., “IT₀”), a first (light press) intensity threshold (e.g.,“IT_(L)”) and a second (deep press) intensity threshold (e.g.,“IT_(D)”).

FIGS. 5A-5G illustrate an example of replacing display of a lower-leveluser interface with a higher-level user interface including displayingan animated transition between the lower-level user interface and thehigher-level user interface. FIGS. 5A-5G illustrate user interfacesdisplayed on display 450 of a device (e.g., device 300) and responsiveto inputs (e.g., a finger contact) on touch-sensitive surface 451. Theinterfaces in FIGS. 5A-5G include home icon 7802 and, in accordance withsome embodiments, a cursor 7808 which is a displayed representation of afocus selector over home icon 7802, corresponding to input 7806 (e.g., acontact). FIGS. 5A-5G also shows the intensity of input 7806. In FIG.5A, the device displays lower-level user interface 7800 that includesbook 7801 and home icon 7802. FIG. 5A further illustrates input 7806with intensity above IT₀ and below IT_(L). FIGS. 5B-5C illustrate ananimated transition between lower-level user interface 7800 in FIG. 5Aand intermediate-level user interface 7804 in FIG. 5D. FIGS. 5B-5Cfurther illustrate the intensity of input 7806 increasing from slightlyabove IT_(L) to slightly below IT_(D). In FIG. 5D the intensity of input7806 is above IT_(L) and below IT_(D) and the device displaysintermediate-level user interface 7804 that includes library 7805. FIGS.5E-5F illustrate an animated transition between intermediate-level userinterface 7804 in FIG. 5D and higher-level user interface 7810 in FIG.5G. FIGS. 5E-5F further illustrate the intensity of input 7806 aboveIT_(D). In FIG. 5G, the device displays higher-level user interface7810, which includes library launch icon 7811 and home icon 7802. FIG.5G further illustrates input 7806 with intensity above IT_(D).

The lower-level and intermediate-level user interfaces are shown inFIGS. 5A-5G as full-screen user interfaces for ease of illustration.However, in some embodiments, the lower-level user interface and/or theintermediate-level user interface are non-full-screen user interfacessuch as drop-down menus, pop-over menus, or other user interfaces thatare displayed over at least a portion the higher-level user interfacewhile still displaying at least a portion of the higher-level userinterface. For example, in FIG. 5A, lower-level user interface 7800 is,optionally, shifted laterally or reduced in size so as to reveal atleast a portion of intermediate-level user interface 7804 (shown in FIG.5D) and/or higher-level user interface 7810 (shown in FIG. 5G).Similarly in FIG. 5D, intermediate-level user interface 7804 is,optionally, shifted laterally or reduced in size so as to reveal atleast a portion of higher-level user interface 7810 (shown in FIG. 5G).Using non-full-screen user interfaces instead of or in addition tofull-screen user interfaces can provide a user with helpful context anda visual indication of what will happen if and when the user provides aninput that is associated with user interface hierarchy navigation (e.g.,a reminder that a press input on the home button will cause the deviceto redisplay the home screen or the library).

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes contactintensity sensor(s) 165 on the display (FIG. 1A).

In some embodiments, a cursor 7808 is a displayed representation offocus selector with a position on display 450 that is determined inaccordance with contacts received by touch-sensitive surface 451. Inother embodiments the focus selector has a different displayedrepresentation (e.g., a magnifying glass). Alternatively, in someembodiments a representation of the focus selector is not displayed. Forexample, in embodiments using a touch-sensitive display system, theposition of the focus selector corresponds to the location on thedisplay of a contact or gesture. Further, the focus selector is hereindefined to be “over” a user interface object when the position of thefocus selector corresponds to the location on the display of the userinterface object.

FIGS. 5H-5J illustrate an example of a user interface hierarchy thatincludes a portion of the touch-sensitive surface that is associatedwith hierarchy navigation. FIGS. 5H-5J illustrate user interfacesdisplayed on touch-sensitive display 7814 of a device. The interfaces inFIGS. 5H-5J include portion 7816 of touch-sensitive display 7814 that isassociated with hierarchy navigation. FIGS. 5H-5J also show input 7820over portion 7816 of touch-sensitive display 7814 and the intensity ofinput 7820. In FIG. 5H, the device displays lower-level user interface7812 that includes child folder 1 contents 7813. FIG. 5H furtherillustrates input 7820 with intensity above IT₀ and below IT_(L). InFIG. 5I, the device displays intermediate-level user interface 7818 thatincludes parent folder 1 contents 7819. FIG. 5I further illustratesinput 7820 with intensity above IT_(L) and below IT_(D). In FIG. 5J, thedevice displays higher-level user interface 7822 that includes folderslaunch icon 7823. FIG. 5J further illustrates input 7820 with intensityabove IT_(D).

FIGS. 5K-5P illustrate an example of a user interface hierarchy thatincludes more than three levels. FIGS. 5K-5P illustrate user interfacesdisplayed on touch screen 112 of portable multifunction device 100. Thedevice in FIGS. 5K-5P includes home button 204 associated with hierarchynavigation. In FIGS. 5K-5L, device 100 displays lower-level userinterface 7824, a media presentation interface, on touch screen 112.FIG. 5L further illustrates input 7828, over home button 204, withintensity above IT₀ and below IT_(L). In FIG. 5M, device 100 displaysintermediate-level user interface 7826, a media collection displayinterface, on touch screen 112. FIG. 5M further illustrates input 7828with intensity above IT_(L) and below IT_(D). In FIG. 5N, device 100displays user interface 7832, another media collection displayinterface, on touch screen 112. In FIG. 5O, the device displayshigher-level user interface 7834, another media collection displayinterface, on touch screen 112. FIG. 5O further illustrates input 7828with intensity above IT_(D). In FIG. 5P, the device displays userinterface 7836 that includes movie application launch icon 7837 on touchscreen 112.

In accordance with some embodiments, FIGS. 5Q-5U illustrate examples ofreplacing a lower-level user interface with a higher-level userinterface in accordance with the duration of an input. FIGS. 5Q-5R showinput 7840 with duration below threshold DT and the device switchingfrom display of lower-level user interface 7800 in FIG. 5Q tohigher-level user interface 7810 in FIG. 5R. Conversely, FIGS. 5S-5Uillustrate input 7842 with duration above threshold DT and the deviceswitching from display of lower-level user interface 7800 in FIG. 5S tointermediate-level user interface 7804 in FIG. 5T to higher-level userinterface 7810 in FIG. 5U.

FIGS. 6A-6D are flow diagrams illustrating method 7900 of navigatinguser interface hierarchies in accordance with some embodiments. Method7900 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the display is a touchscreen display and the touch-sensitive surface is on the display. Insome embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 7900 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, method 7900 provides an intuitive way to navigateuser interface hierarchies. The method reduces the cognitive burden on auser when navigating user interface hierarchies, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to navigate user interface hierarchies fasterand more efficiently conserves power and increases the time betweenbattery charges.

The device displays (7902), on the display, a lower-level user interfacethat is part of a user interface hierarchy. The hierarchy includes(7904) at least three levels, including the lower-level user interface,an intermediate-level user interface and a higher-level user interface.The intermediate-level user interface is above the lower-level userinterface in the hierarchy. The higher-level user interface is aboveboth the intermediate-level user interface and the lower-level userinterface in the hierarchy. In FIG. 5A, for example, the device displayslower-level user interface 7800 including book 7801. In this example,FIG. 5D illustrates intermediate-level user interface 7804 and FIG. 5Gillustrates higher-level user interface 7810.

In some embodiments, the hierarchy includes (7906) exactly three levelsin order from highest to lowest: the higher-level user interface; theintermediate-level user interface; and the lower-level user interface.For example, in these embodiments, lower-level user interface 7812 inFIG. 5H, intermediate-level user interface 7818 in FIG. 5I, andhigher-level user interface 7822 in FIG. 5J are a complete userinterface hierarchy with exactly three levels.

In some embodiments, the higher-level user interface is (7908) adjacentto the intermediate-level user interface in the hierarchy, and theintermediate-level user interface is adjacent to the lower-level userinterface in the hierarchy. For example, in these embodiments,lower-level user interface 7800 in FIG. 5A is adjacent tointermediate-level user interface 7804 in FIG. 5D and higher-level userinterface 7810 in FIG. 5G is adjacent to intermediate-level userinterface 7804 in FIG. 5D.

In some embodiments, the hierarchy includes (7910) more than threelevels. For example, one or more levels above the higher-level userinterface, one or more levels between the higher-level user interfaceand the intermediate-level user interface, one or more levels betweenthe intermediate-level user interface and the lower-level userinterface, and/or one or more levels below the lower-level userinterface, or any combination thereof. FIGS. 5L-5P, for example,illustrate a user interface hierarchy with more than three levels. FIG.5L illustrates lower-level user interface 7824, FIG. 5M illustratesintermediate-level user interface 7826, and FIG. 5O, in theseembodiments, illustrates higher-level user interface 7834. In addition,FIG. 5N illustrates user interface 7832 between intermediate-level userinterface 7826 and higher-level user interface 7834 and FIG. 5Pillustrates user interface 7836 above higher-level user interface 7834.

In some embodiments, the lower-level and intermediate-level userinterfaces are (7912) user interfaces in a single application (e.g., abook, music, video or other media application). The higher-level userinterface is an application launch user interface. (e.g., a homescreen). For example, FIGS. 5A-5G illustrate a user interface hierarchyinvolving a book application. FIG. 5A illustrates lower-level userinterface 7800 including book 7801. FIG. 5D illustratesintermediate-level user interface 7804 including book library 7805. FIG.5G illustrates higher-level user interface 7810 including bookapplication launch icon 7811.

In some embodiments, the lower-level, intermediate-level andhigher-level user interfaces are (7914) user interfaces in a singleapplication. FIGS. 5L-5O illustrate an example where the lower-level,intermediate-level and higher-level user interfaces are user interfacesin a single application. FIG. 5L illustrates lower-level user interface7824, FIG. 5M illustrates intermediate-level user interface 7826, andFIG. 5O, in these embodiments, illustrates higher-level user interface7834, all of which are user interfaces for a movie application.

In some embodiments, the lower-level user interface is (7916) a mediapresentation interface (e.g., text, image, video or audio playback). Theintermediate-level user interface is a media collection displayinterface (e.g., music/book/photo/video library, reading list, orplaylist) of a media player application. The higher-level user interfaceis an application launch user interface (e.g., desktop or home screen)that includes an icon representing the media player application. Forexample, FIG. 5L illustrates lower-level user interface 7824 (a mediapresentation interface), FIG. 5M illustrates intermediate-level userinterface 7826 (a media collection display interface), and FIG. 5P, inthese embodiments, illustrates higher-level user interface 7836 (anapplication launch user interface).

In some embodiments, the lower-level user interface is (7918) asubfolder. The intermediate-level user interface is a folder containingthe subfolder. The higher-level user interface is an application launchinterface (e.g., a homescreen or desktop including one or moreapplication launch icons) that includes an icon representing the folder.For example, FIG. 5H illustrates lower-level user interface 7812including child folder 1 contents 7813 (a subfolder), FIG. 5Iillustrates intermediate-level user interface 7818 including parentfolder contents 7819 (a folder containing the subfolder), and FIG. 5Jillustrates higher-level user interface 7822 that includes folders icon7823 (an application launch interface that includes an icon representingthe folder).

The device, while displaying the lower-level user interface, detects(7920) an input on a portion of the device that is associated with userinterface hierarchy navigation (e.g., an icon on a touch-screen display,a region on a touch-sensitive surface, or a physical button withintegrated intensity sensor(s)). For example, FIG. 5A illustrateslower-level user interface 7800 displayed on display 450 and input 7806detected on touch-sensitive surface 451. FIG. 5A further illustrates acursor 7808 which is a displayed representation of a focus selector,corresponding to input 7806, over home icon 7802.

In some embodiments, the portion of the device on which the input isdetected is (7922) a physical button (e.g., home button 204, FIG. 5K).For example, FIG. 5L illustrates input 7828 over home button 204 ofportable multifunction device 100.

In some embodiments, the portion of the device on which the input isdetected is (7924) a portion of the touch-sensitive surface that isassociated with hierarchy navigation. For example, in FIG. 5H, input7820 is detected over portion 7816 of user interface 7812. In thisexample, portion 7816 of user interface 7812 is associated withhierarchy navigation.

In some embodiments, the portion of the device on which the input isdetected is (7926) a portion of a touch screen display that includes anicon associated with hierarchy navigation (e.g., a “back” button in auser interface). For example, FIG. 5A illustrates input 7806 detected ontouch-sensitive surface 451. FIG. 5A further illustrates a cursor 7808which is a displayed representation of a focus selector), correspondingto input 7806, over home icon 7802. In this example, home icon 7802 isassociated with hierarchy navigation.

In some embodiments, the input is (7928) a contact on a touch-sensitivesurface. For example, in FIG. 5H input 7820 (a contact) is detected ontouch-sensitive display 7814.

In some embodiments, the input includes a contact detected on thetouch-sensitive surface and the input is (7930) a stationary gesture(e.g., a stationary press input) that does not include lateral movementof the contact on the touch-sensitive surface. For example, in FIG. 5Hthe device detects input 7820 on touch-sensitive display 7814 withoutany lateral movement.

In response to detecting the input (7932), in accordance with adetermination that the input meets first transition criteria (e.g., asingle-step-transition intensity threshold) that include a criterionthat a maximum intensity of the input is above a first intensitythreshold (e.g., an activation intensity threshold) and below a secondintensity threshold (e.g., a multi-step-transition intensity threshold),where the second intensity threshold is higher than the first intensitythreshold, the device replaces (7934) display of the lower-level userinterface with display of the intermediate-level user interface (whichcauses the device to cease to display the lower-level user interface).For example, in FIG. 5D input 7806 has intensity above IT_(L) and belowIT_(D) and the device replaces lower-level interface 7800 (in FIG. 5A)with intermediate-level interface 7804.

In response to detecting the input (7932), in accordance with adetermination that the input meets second transition criteria thatinclude a criterion that a maximum intensity of the input is above thesecond intensity threshold, the device replaces (7936) display of thelower-level user interface with display of the higher-level userinterface (which causes the device to cease to display the lower-leveluser interface). For example, in FIG. 5G input 7806 has intensity aboveIT_(D) and the device replaces lower-level interface 7800 (in FIG. 5A)with higher-level interface 7810.

In some embodiments, replacing display of the lower-level user interfacewith the higher-level user interface includes (7938) displaying ananimated transition between the lower-level user interface and thehigher-level user interface where the animated transition progresses ata rate that corresponds to the intensity of the input. For example, aplurality of speeds of progressing through the animated transition aremapped to corresponding contact intensity values of a plurality ofdetectable contact intensity values, and the speed of progression of theanimated transition increases as the intensity of the input increases.In these embodiments the animated transition illustrated in FIGS. 5A-5Gprogresses at a rate corresponding to the intensity of input 7806.

In some embodiments, replacing display of the lower-level user interfacewith the higher-level user interface includes (7940) displaying ananimated transition between the lower-level user interface and thehigher-level user interface where the animated transition progresses inaccordance with the intensity of the input. For example, a plurality ofstates of the animation are mapped to corresponding contact intensityvalues of a plurality of detectable contact intensity values, and theanimated transition progresses as the intensity of the input increasesfrom a first intensity threshold to a second intensity threshold higherthan the first intensity threshold. In these embodiments the animatedtransition illustrated in FIGS. 5A-5G progresses as the intensity ofinput 7806 increases from intensity above IT₀ and below IT_(L) in FIG.5A to intensity above IT_(D) in FIG. 5G.

In some embodiments, replacing display of the lower-level user interfacewith the higher-level user interface includes (7942) displaying ananimated transition between the lower-level user interface and thehigher-level user interface that includes displaying a representation ofthe intermediate-level user interface. In these embodiments, if thetransition is between two non-adjacent levels of the hierarchy (e.g.,the lower-level user interface and the higher-level user interface),when displaying the animated transition, the device displays one or moreinterstitial user interfaces between the two non-adjacent levels of thehierarchy to provide context for the user as to the navigation withinthe hierarchy. For example, in accordance with these embodiments, theanimated transition illustrated in FIGS. 5A-5G includes display ofintermediate-level interface 7804.

In some embodiments, the device determines (7944) whether the input hasa duration longer than a respective time threshold. Replacing display ofthe lower-level user interface with display of the higher-level userinterface includes, in accordance with a determination that the inputhas a duration longer than the respective time threshold, switching(7946) from displaying the lower-level user interface to displaying arepresentation of the intermediate-level user interface to displayingthe higher-level user interface. For example, in response to detecting aslow press input, the device switches from displaying the lower-leveluser interface to displaying the intermediate-level user interface andthen to displaying the higher-level user interface. FIGS. 5S-5U, forexample, illustrate input 7842 with duration above threshold DT and thedevice switching from display of lower-level user interface 7800 in FIG.5S to intermediate-level user interface 7804 in FIG. 5T to higher-leveluser interface 7810 in FIG. 5U.

Conversely, in some embodiments, the device determines (7944) whetherthe input has a duration longer than a respective time threshold.Replacing display of the lower-level user interface with display of thehigher-level user interface includes, in accordance with a determinationthat the input has a duration shorter than the respective timethreshold, replacing (7948) display of the lower-level user interfacewith display of the higher-level user interface without displaying arepresentation the intermediate-level user interface For example, inresponse to detecting a quick tap input, the device switches directlyfrom the lower-level user interface to the higher-level user interface.FIGS. 5Q-5R, for example, illustrate input 7840 with duration belowthreshold DT and the device switching from display of lower-level userinterface 7800 in FIG. 5Q to higher-level user interface 7810 in FIG.5R.

It should be understood that the particular order in which theoperations in FIGS. 6A-6D have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 7900 describedabove with respect to FIGS. 6A-6D. For example, the inputs, contacts,intensity thresholds, duration thresholds, user interfaces, focusselectors, icons, and buttons described above with reference to method7900 optionally have one or more of the characteristics of the inputs,contacts, intensity thresholds, duration thresholds, user interfaces,focus selectors, icons, and buttons described herein with reference toother methods described herein (e.g., those listed in the fifthparagraph of the Description of Embodiments). For brevity, these detailsare not repeated here.

In accordance with some embodiments, FIG. 7 shows a functional blockdiagram of an electronic device 8000 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 7 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 7, electronic device 8000 includes display unit 8002configured to display a lower-level user interface that is part of auser interface hierarchy, where: the hierarchy includes at least threelevels, including the lower-level user interface, an intermediate-leveluser interface and a higher-level user interface; the intermediate-leveluser interface is above the lower-level user interface in the hierarchy;and the higher-level user interface is above both the intermediate-leveluser interface and the lower-level user interface in the hierarchy.Electronic device 8000 further includes touch-sensitive surface unit8004 configured to receive user inputs; one or more sensor units 8005configured to detect intensity of contacts with the touch-sensitivesurface unit; and a processing unit 8006 coupled to the display unit8002, the touch-sensitive surface unit 8004, and the sensor units 8005.In some embodiments, processing unit 8006 includes detecting unit 8008,replacing unit 8010, determining unit 8012, switching unit 8014, anddisplay enabling unit 8016.

Processing unit 8006 is configured to, while displaying the lower-leveluser interface, detect an input (e.g., with detecting unit 8008) on aportion of the device that is associated with user interface hierarchynavigation. Processing unit 8006 is further configured to, in responseto detecting the input, in accordance with a determination that theinput meets first transition criteria that include a criterion that amaximum intensity of the input is above a first intensity threshold andbelow a second intensity threshold, where the second intensity thresholdis higher than the first intensity threshold, replace (e.g., withreplacing unit 8010) display of the lower-level user interface withdisplay of the intermediate-level user interface and, in accordance witha determination that the input meets second transition criteria thatinclude a criterion that a maximum intensity of the input is above thesecond intensity threshold, replace (e.g., with replacing unit 8010)display of the lower-level user interface with display of thehigher-level user interface.

In some embodiments, the portion of the device on which the input isdetected (e.g., with detecting unit 8008) is a physical button.

In some embodiments, the portion of the device on which the input isdetected (e.g., with detecting unit 8008) is a portion of thetouch-sensitive surface unit that is associated with hierarchynavigation.

In some embodiments, the portion of the device on which the input isdetected (e.g., with detecting unit 8008) is a portion of a touch screendisplay unit that includes an icon associated with hierarchy navigation.

In some embodiments, the input is a contact on a touch-sensitive surfaceunit.

In some embodiments, the input includes a contact detected (e.g., withdetecting unit 8008) on the touch-sensitive surface unit and the inputis a stationary gesture that does not include lateral movement of thecontact on the touch-sensitive surface unit.

In some embodiments, the hierarchy includes exactly three levels inorder from highest to lowest: the higher-level user interface; theintermediate-level user interface; and the lower-level user interface.

In some embodiments, the higher-level user interface is adjacent to theintermediate-level user interface in the hierarchy and theintermediate-level user interface is adjacent to the lower-level userinterface in the hierarchy.

In some embodiments, the hierarchy includes more than three levels.

In some embodiments, the lower-level and intermediate-level userinterfaces are user interfaces in a single application and thehigher-level user interface is an application launch user interface.

In some embodiments, the lower-level, intermediate-level andhigher-level user interfaces are user interfaces in a singleapplication.

In some embodiments, the lower-level user interface is a mediapresentation interface, the intermediate-level user interface is a mediacollection display interface of a media player application, and thehigher-level user interface is an application launch user interface thatincludes an icon representing the media player application.

In some embodiments, the lower-level user interface is a subfolder, theintermediate-level user interface is a folder containing the subfolder,and the higher-level user interface is an application launch interfacethat includes an icon representing the folder.

In some embodiments, replacing (e.g., with replacing unit 8010) displayof the lower-level user interface with the higher-level user interfaceincludes enabling display of (e.g., with display enabling unit 8016) ananimated transition between the lower-level user interface and thehigher-level user interface where the animated transition progresses ata rate that corresponds to the intensity of the input.

In some embodiments, replacing (e.g., with replacing unit 8010) displayof the lower-level user interface with the higher-level user interfaceincludes enabling display of (e.g., with display enabling unit 8016) ananimated transition between the lower-level user interface and thehigher-level user interface where the animated transition progresses inaccordance with the intensity of the input.

In some embodiments, replacing (e.g., with replacing unit 8010) displayof the lower-level user interface with the higher-level user interfaceincludes enabling display of an animated transition between thelower-level user interface and the higher-level user interface thatincludes enabling display of (e.g., with display enabling unit 8016) arepresentation of the intermediate-level user interface.

In some embodiments, processing unit 8006 is further configured todetermine (e.g., with determining unit 8012) whether the input has aduration longer than a respective time threshold, and replacing (e.g.,with replacing unit 8008) display of the lower-level user interface withdisplay of the higher-level user interface includes, in accordance witha determination that the input has a duration longer than the respectivetime threshold, switching (e.g., with switching unit 8014) from enablingdisplay of the lower-level user interface to enabling display of arepresentation of the intermediate-level user interface and thenenabling display of the higher-level user interface, and in accordancewith a determination that the input has a duration shorter than therespective time threshold, replacing (e.g., with replacing unit 8008)display of the lower-level user interface with display of thehigher-level user interface without enabling display of a representationthe intermediate-level user interface.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 6A-6D are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 7.For example, detection operation 7920, replacing operation 7934,replacing operation 7936 and switching operation 7946 are, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

Navigating User Interface Hierarchies

Many electronic devices have graphical user interfaces that includevarious user interface hierarchies and it is easy for a user to losetheir place within the user interface hierarchy or become confused as tohow to navigate through the user interface hierarchy. For example, amedia player application includes several interfaces for users tonavigate between. In this example, the media player application's userinterface hierarchy includes a media presentation interface, a mediacollection display interface, and a user interface with an applicationlaunch icon for the media player application (e.g., a home or startinginterface). The embodiments below improve on these methods by reducingthe cognitive burden on a user and produce an intuitive and efficienthuman-machine interface by determining, based on a duration of adetected input, whether to navigate through a user interface hierarchyin accordance with an intensity of the detected input and provide visualfeedback indicative of the navigation through the user interfacehierarchy or to navigate through the user interface hierarchy usingdifferent feedback.

FIGS. 8A-8V illustrate exemplary user interfaces for navigating a userinterface hierarchy using inputs on a touch-sensitive surface inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses described below with reference to FIGS. 9A-9E. FIGS. 8C-8Vinclude intensity diagrams that show the current intensity of thecontact on the touch-sensitive surface relative to a plurality ofintensity thresholds including a contact detection intensity threshold(e.g., “IT₀”), a first (light press) intensity threshold (e.g.,“IT_(L)”) and a second (deep press) intensity threshold (e.g.,“IT_(D)”).

FIGS. 8A-8B illustrate an example of replacing display of a lower-leveluser interface with a higher-level user interface. In this example theduration of input 8105 is below a predefined threshold (e.g., a tapgesture). FIGS. 8A-8B illustrate user interfaces displayed on display450 of a device (e.g., device 300) and responsive to inputs (e.g., afinger contact) on touch-sensitive surface 451. The interfaces in FIGS.8A-8I include home icon 8102 and, in accordance with some embodiments, acursor 8108 is a displayed representation of focus selector over homeicon 8102, corresponding to input 8105 (e.g., a contact). In FIG. 8A,the device displays lower-level user interface 8100 including book 8101and home icon 8102. FIG. 8A further illustrates the device detectinginput 8105 on touch-sensitive surface 451. In FIG. 8B the device detectsliftoff of input 8105 and, because the duration of input 8105 is belowthe predefined threshold, the device replaces display of lower-levelinterface 8100 with display of higher-level interface 8110.

FIGS. 8C-8I illustrate an example of replacing display of lower-leveluser interface with a higher-level user interface including displayingan animated transition between the lower-level user interface and thehigher-level user interface. In this example the duration of input 8106is above a predefined threshold. In FIG. 8C the device displayslower-level user interface 8100 including book 8101 and home icon 8102.FIG. 8C further illustrates the device detecting input 8106 withintensity above IT₀ and below IT_(L) on touch-sensitive surface 451.FIGS. 8D-8E illustrate an animated transition between lower-level userinterface 8100 in FIG. 8C and intermediate-level user interface 8104 inFIG. 8F. FIGS. 8D-8E further illustrate the intensity of input 8106increasing from slightly above IT_(L) to slightly below IT_(D). In FIG.8F the intensity of input 8106 is above IT_(L) and below IT_(D) and thedevice displays intermediate-level user interface 8104 that includeslibrary 8105. FIGS. 8G-8H illustrate an animated transition betweenintermediate-level user interface 8104 in FIG. 8F and higher-level userinterface 8110 in FIG. 8I. FIGS. 8G-8H further illustrate the intensityof input 8106 above IT_(D). In FIG. 8I, the device displays higher-leveluser interface 8110, which includes library launch icon 8111 and homeicon 8102. FIG. 8I further illustrates input 8106 with intensity aboveIT_(D).

The lower-level and intermediate-level user interfaces are shown inFIGS. 8C-8I as full-screen user interfaces for ease of illustration.However, in some embodiments, the lower-level user interface and/or theintermediate-level user interface are non-full-screen user interfacessuch as drop-down menus, pop-over menus, or other user interfaces thatare displayed over at least a portion the higher-level user interfacewhile still displaying at least a portion of the higher-level userinterface. For example, in FIG. 8C, lower-level user interface 8100 is,optionally, shifted laterally or reduced in size so as to reveal atleast a portion of intermediate-level user interface 8104 (shown in FIG.8F) and/or higher-level user interface 8110 (shown in FIG. 8I).Similarly in FIG. 8F, intermediate-level user interface 8104 is,optionally, shifted laterally or reduced in size so as to reveal atleast a portion of higher-level user interface 8110 (shown in FIG. 8I).Using non-full-screen user interfaces instead of or in addition tofull-screen user interfaces can provide a user with helpful context anda visual indication of what will happen if and when the user provides aninput that is associated with user interface hierarchy navigation (e.g.,a reminder that a tap on the home button will cause the device toredisplay the home screen).

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes contactintensity sensor(s) 165 on the display (FIG. 1A).

In some implementations, a cursor 8108 is a displayed representation ofa focus selector with a position on display 450 that is determined inaccordance with contacts received by touch-sensitive surface 451. Inother implementations the focus selector has a different displayedrepresentation (e.g., a magnifying glass). Alternatively, in someimplementations a representation of the focus selector is not displayed.For example, in implementations using a touch-sensitive display system,the position of the focus selector corresponds to the location on thedisplay of a contact or gesture. Further, the focus selector is hereindefined to be “over” a user interface object when the position of thefocus selector corresponds to the location on the display of the userinterface object.

FIGS. 8J-8K illustrate an example of a user interface hierarchy thatincludes a portion of the touch-sensitive surface that is associatedwith hierarchy navigation. In this example the duration of input 8119 isbelow a predefined threshold (e.g., a tap gesture). FIGS. 8J-8Killustrate user interfaces displayed on touch-sensitive display 8114 ofa device. The interfaces in FIGS. 8J-8K include portion 8116 oftouch-sensitive display 8114 that is associated with hierarchynavigation. FIGS. 8J-8K also show input 8119 over portion 8116 oftouch-sensitive display 8114. In FIG. 8J, the device displayslower-level user interface 8112 including child folder 1 contents 8113.In FIG. 8K the device detects liftoff of input 8119 and, because theduration of input 8119 is below the predefined threshold, the devicereplaces display of lower-level interface 8112 with display ofhigher-level interface 8122.

FIGS. 8L-8N illustrate another example of a user interface hierarchythat includes a portion of the touch-sensitive surface that isassociated with hierarchy navigation. In this example the duration ofinput 8120 is above a predefined threshold. In FIG. 8L, the devicedisplays lower-level user interface 8112 that includes child folder 1contents 8113. FIG. 8L further illustrates input 8120 with intensityabove IT₀ and below IT_(L). In FIG. 8M, the device displaysintermediate-level user interface 8118 that includes parent folder 1contents 8121. FIG. 8M further illustrates input 8120 with intensityabove IT_(L) and below IT_(D). In FIG. 8N, the device displayshigher-level user interface 8122 that includes folders launch icon 8123.FIG. 8N further illustrates input 8120 with intensity above IT_(D).

FIGS. 8O-8Q illustrate an example of navigating a user interfacehierarchy on a portable multifunction device. In this example theduration of input 8127 is below a predefined threshold (e.g., a tapgesture). FIGS. 8O-8Q illustrate user interfaces displayed on touchscreen 112 of portable multifunction device 100. The device in FIGS.8O-8Q includes home button 204 associated with hierarchy navigation. InFIGS. 8O-8P, device 100 displays lower-level user interface 8124, amedia presentation interface, on touch screen 112. FIG. 8P furtherillustrates input 8127 over home button 204. In FIG. 8Q the devicedetects liftoff of input 8127 and, because the duration of input 8127 isbelow the predefined threshold, the device replaces display oflower-level interface 8124 with display of higher-level interface 8134.

FIGS. 8R-8V illustrate an example of navigating a user interfacehierarchy that includes more than three levels, on a portablemultifunction device. In this example the duration of input 8128 isabove a predefined threshold. In FIG. 8R, device 100 displayslower-level user interface 8124, a media presentation interface, ontouch screen 112. FIG. 8R further illustrates input 8128, over homebutton 204, with intensity above IT₀ and below IT_(L). In FIG. 8S,device 100 displays intermediate-level user interface 8126, a mediacollection display interface, on touch screen 112. FIG. 8S furtherillustrates input 8128 with intensity above IT_(L) and below IT_(D). InFIG. 8T, device 100 displays user interface 8132, another mediacollection display interface, on touch screen 112. In FIG. 8U, thedevice displays higher-level user interface 8134, another mediacollection display interface, on touch screen 112. FIG. 8U furtherillustrates input 8128 with intensity above IT_(D). In FIG. 8V, thedevice displays user interface 8136 that includes movie applicationlaunch icon 8137 on touch screen 112.

FIGS. 9A-9E are flow diagrams illustrating method 8200 of navigatinguser interface hierarchies in accordance with some embodiments. Method8200 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the display is a touchscreen display and the touch-sensitive surface is on the display. Insome embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 8200 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, method 8200 provides an intuitive way to navigateuser interface hierarchies. The method reduces the cognitive burden on auser when navigating user interface hierarchies, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to navigate user interface hierarchies fasterand more efficiently conserves power and increases the time betweenbattery charges.

The device displays (8202), on the display, a lower-level user interfacethat is part of a user interface hierarchy. The hierarchy includes(8204) at least three levels, including the lower-level user interface,an intermediate-level user interface and a higher-level user interface.The intermediate-level user interface is above the lower-level userinterface in the hierarchy. The higher-level user interface is aboveboth the intermediate-level user interface and the lower-level userinterface in the hierarchy. In FIG. 8C, for example, the device displayslower-level user interface 8100 including book 8101. In this example,FIG. 8F illustrates intermediate-level user interface 8104 and FIG. 8Iillustrates higher-level user interface 8110.

In some embodiments, the hierarchy includes (8206) exactly three levelsin order from highest to lowest: the higher-level user interface; theintermediate-level user interface; and the lower-level user interface.For example, in these embodiments, lower-level user interface 8112 inFIG. 8L, intermediate-level user interface 8118 in FIG. 8M, andhigher-level user interface 8122 in FIG. 8N are a complete userinterface hierarchy with exactly three levels.

In some embodiments, the higher-level user interface is (8208) adjacentto the intermediate-level user interface in the hierarchy and theintermediate-level user interface is adjacent to the lower-level userinterface in the hierarchy. For example, in these embodiments,lower-level user interface 8100 in FIG. 8C is adjacent tointermediate-level user interface 8104 in FIG. 8F and higher-level userinterface 8110 in FIG. 8I is adjacent to intermediate-level userinterface 8104 in FIG. 8F.

In some embodiments, the hierarchy includes (8210) more than threelevels. For example, one or more levels above the higher-level userinterface, one or more levels between the higher-level user interfaceand the intermediate-level user interface, one or more levels betweenthe intermediate-level user interface and the lower-level userinterface, and/or one or more levels below the lower-level userinterface, or any combination thereof. FIGS. 8R-8V, for example,illustrate a user interface hierarchy with more than three levels. FIG.8R illustrates lower-level user interface 8124, FIG. 8T illustratesintermediate-level user interface 8126, and FIG. 8U, in theseembodiments, illustrates higher-level user interface 8134. In addition,FIG. 8S illustrates user interface 8132 between intermediate-level userinterface 8126 and higher-level user interface 8134 and FIG. 8Villustrates user interface 8136 above higher-level user interface 8134.

In some embodiments, the lower-level and intermediate-level userinterfaces are (8212) user interfaces in a single application (e.g., abook, music, video or other media application). The higher-level userinterface is an application launch user interface. (e.g., a homescreen). For example, FIGS. 8C-8I illustrate a user interface hierarchyinvolving a book application. FIG. 8C illustrates lower-level userinterface 8100 including book 8101. FIG. 8F illustratesintermediate-level user interface 8104 including book library 8105. FIG.8I illustrates higher-level user interface 8110 including bookapplication launch icon 8111.

In some embodiments, the lower-level, intermediate-level andhigher-level user interfaces are (8214) user interfaces in a singleapplication. FIGS. 8R-8U illustrate an example where the lower-level,intermediate-level and higher-level user interfaces are user interfacesin a single application. FIG. 8R illustrates lower-level user interface8124, FIG. 8S illustrates intermediate-level user interface 8126, andFIG. 8U, in these embodiments, illustrates higher-level user interface8134, all of which are user interfaces for a movie application.

In some embodiments, the lower-level user interface is (8216) a mediapresentation interface (e.g., text, image, video or audio playback). Theintermediate-level user interface is a media collection displayinterface (e.g., music/book/photo/video library, reading list, orplaylist) of a media player application. The higher-level user interfaceis an application launch user interface (e.g., desktop or home screen)that includes an icon representing the media player application. Forexample, FIG. 8R illustrates lower-level user interface 8124 (a mediapresentation interface), FIG. 8S illustrates intermediate-level userinterface 8126 (a media collection display interface), and FIG. 8V, inthese embodiments, illustrates higher-level user interface 8136 (anapplication launch user interface).

In some embodiments, the lower-level user interface is (8218) asubfolder. The intermediate-level user interface is a folder containingthe subfolder. The higher-level user interface is an application launchinterface (e.g., a homescreen or desktop including one or moreapplication launch icons) that includes an icon representing the folder.For example, FIG. 8L illustrates lower-level user interface 8112including child folder 1 contents 8113 (a subfolder), FIG. 8Millustrates intermediate-level user interface 8118 including parentfolder contents 8121 (a folder containing the subfolder), and FIG. 8Nillustrates higher-level user interface 8122 that includes folders icon8123 (an application launch interface that includes an icon representingthe folder).

The device, while displaying the lower-level user interface, detects(8220) an input on a portion of the device that is associated with userinterface hierarchy navigation (e.g., an icon on a touch-screen display,a region on a touch-sensitive surface, or a physical button withintegrated intensity sensor(s)). For example, FIG. 8A illustrateslower-level user interface 8100 displayed on display 450 and input 8105detected on touch-sensitive surface 451. FIG. 8A further illustrates acursor 8108 is a displayed representation of a focus selectorcorresponding to input 8105, over home icon 8102.

In some embodiments, the portion of the device on which the input isdetected is (8222) a physical button (e.g., home button 204, FIG. 8O).For example, FIG. 8P illustrates input 8127 over home button 204 ofportable multifunction device 100.

In some embodiments, the portion of the device on which the input isdetected is (8224) a portion of the touch-sensitive surface that isassociated with hierarchy navigation. For example, in FIG. 8J, input8119 is detected over portion 8116 of user interface 8112. In thisexample, portion 8116 of user interface 8112 is associated withhierarchy navigation.

In some embodiments, the portion of the device on which the input isdetected is (8226) a portion of a touch screen display that includes anicon associated with hierarchy navigation (e.g., a “back” button in auser interface). For example, FIG. 8A illustrates input 8105 detected ontouch-sensitive surface 451. FIG. 8A further illustrates a cursor is adisplayed representation of a focus selector corresponding to input8105, over home icon 8102. In this example, home icon 8102 is associatedwith hierarchy navigation.

In some embodiments, the input is (8228) a contact on a touch-sensitivesurface. For example, in FIG. 8J input 8119 (e.g., a contact) isdetected on touch-sensitive display 8114.

In some embodiments, the input includes a contact detected on thetouch-sensitive surface. The input is (8230) a stationary gesture (e.g.,a stationary press input) that does not include lateral movement of thecontact on the touch-sensitive surface. For example, in FIG. 8J input8119 is detected on touch-sensitive display 8114 and consists of acontact without any lateral movement.

In response to detecting the input (8232), in accordance with adetermination that the input has a duration shorter than a respectivetime threshold (e.g., the input is a tap gesture), the device replaces(8234) display of the lower-level user interface with display of thehigher-level user interface. In some embodiments, as long as the inputhas a duration shorter than the respective time threshold, thelower-level user interface is replaced with the higher-level userinterface without consideration of an amount of intensity by which theinput exceeds an input detection threshold. For example, in FIGS. 8A-8Binput 8105 has a duration below a respective time threshold and thedevice replaces lower-level interface 8100 in FIG. 8A with higher-levelinterface 8110 in FIG. 8B.

In some embodiments, when the input has a duration shorter than therespective time threshold, the device displays (8236) a transitionbetween the lower-level user interface and the higher-level userinterface that does not include displaying a representation of theintermediate-level user interface. For example, FIGS. 8A-8B illustrate atransition between lower-level user interface 8100 in FIG. 8A andhigher-level user interface 8110 in FIG. 8B, in response to the devicedetecting input 8105 with a duration shorter than a respective timethreshold.

In response to detecting the input (8232), in accordance with adetermination that the input has a duration longer than the respectivetime threshold (e.g., the input is a long press gesture), the devicereplaces (8238) display of the lower-level user interface with displayof a respective user interface in the user interface hierarchy selectedin accordance with an intensity of the input. In some of theseembodiments, if the input is a tap gesture, the device responds asthough a user had pressed a physical button quickly by performing adiscrete operation (replacing display of the lower-level user interfacewith display of the higher-level user interface), whereas if the inputis a long press gesture, the device provides intensity feedback byperforming an operation that is based on a detected intensity of theinput (replacing display of the lower-level user interface with displayof a respective user interface in the user interface hierarchy, such asthe intermediate-level user interface or the higher-level userinterface, depending on the intensity of the input), where the detectedintensity is within a range of contact intensity values that aredetectable by the device. For example, in FIG. 8I input 8106 hasintensity above IT_(D) and the device replaces lower-level interface8100 (in FIG. 8A) with intermediate-level interface 8104.

In some embodiments, replacing display of the lower-level user interfacewith display of the respective user interface selected in accordancewith the intensity of the input includes (8240) displaying an animatedtransition between the lower-level user interface and the respectiveuser interface where the animated transition progresses at a rate thatcorresponds to the intensity of the input. For example, a plurality ofspeeds of progressing through the animated transition are mapped tocorresponding contact intensity values of a plurality of detectablecontact intensity values, and the speed of progression of the animatedtransition increases as the intensity of the input increases. In theseembodiments the animated transition illustrated in FIGS. 8C-8Iprogresses at a rate corresponding to the intensity of input 8106.

In some embodiments, replacing display of the lower-level user interfacewith display of the respective user interface selected in accordancewith the intensity of the input includes (8242) displaying an animatedtransition between the lower-level user interface and the respectiveuser interface where the animated transition progresses in accordancewith the intensity of the input. For example, a plurality of states ofthe animation are mapped to corresponding contact intensity values of aplurality of detectable contact intensity values, and the animatedtransition progresses as the intensity of the input increases from afirst intensity threshold to a second intensity threshold higher thanthe first intensity threshold. In these embodiments the animatedtransition illustrated in FIGS. 8C-8I progresses as the intensity ofinput 8106 increases from intensity above IT₀ and below IT_(L) in FIG.8C to intensity above IT_(D) in FIG. 8I.

In some embodiments, replacing display of the lower-level user interfacewith display of the respective user interface selected in accordancewith the intensity of the input, such that the respective user interfaceis the higher level user interface, includes (8244) displaying ananimated transition between the lower-level user interface and thehigher-level user interface that includes displaying a representation ofthe intermediate-level user interface. In these embodiments, if thetransition is between two non-adjacent levels of the hierarchy (e.g.,the lower-level user interface and the higher-level user interface),when displaying the animated transition, the device displays one or moreinterstitial user interfaces between the two non-adjacent levels of thehierarchy to provide context for the user as to the navigation withinthe hierarchy. For example, in accordance with these embodiments, theanimated transition illustrated in FIGS. 8C-8I includes display ofintermediate-level interface 8104 in FIG. 8F.

In some embodiments, replacing display of the lower-level user interfacewith display of the respective user interface selected in accordancewith the intensity of the input (8246) includes, in accordance with adetermination that the input has an intensity above a first intensitythreshold (e.g., a single-step-transition intensity threshold) and belowa second intensity threshold higher than the first intensity threshold,replacing (8248) display of the lower-level user interface with displayof the intermediate-level user interface (e.g., if the input has anintensity between the first intensity threshold and the second intensitythreshold, the respective user interface is the intermediate-level userinterface). For example, in FIG. 8F the intensity of contact 8106 isabove IT_(L) and below IT_(D) and the device replaces lower-level userinterface 8100 in FIG. 8A with intermediate-level user interface 8104.

In some embodiments, replacing display of the lower-level user interfacewith display of the respective user interface selected in accordancewith the intensity of the input (8246) includes, in accordance with adetermination that the input has an intensity above the second intensitythreshold (e.g., a multi-step-transition intensity threshold), replacing(8250) display of the lower-level user interface with display of thehigher-level user interface (e.g., if the input has an intensity abovethe second intensity threshold, the respective user interface is thehigher-level user interface). For example, in FIG. 8I the intensity ofcontact 8106 is above IT_(D) and the device replaces lower-level userinterface 8100 in FIG. 8A with higher-level user interface 8110.

In some embodiments, when the input has a duration longer than therespective time threshold, and replacing display of the lower-level userinterface with display of a respective user interface includes replacingdisplay of the lower-level user interface with the higher-level userinterface, the device displays (8252) a transition between thelower-level user interface and the higher-level user interface thatincludes displaying a representation of the intermediate-level userinterface. For example, in accordance with these embodiments, FIGS.8C-8I illustrate a transition between display of lower-level userinterface 8100 and higher-level user interface 8110 including display ofintermediate-level interface 8104 in FIG. 8F.

Conversely, in some embodiments, when the input has a duration longerthan the respective time threshold and replacing display of thelower-level user interface with display of a respective user interfaceincludes replacing display of the lower-level user interface with thehigher-level user interface, the device displays (8254) a transitionbetween the lower-level user interface and the higher-level userinterface that does not include displaying a representation of theintermediate-level user interface.

It should be understood that the particular order in which theoperations in FIGS. 9A-9E have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 8200 describedabove with respect to FIGS. 9A-9E. For example, the inputs, contacts,intensity thresholds, duration thresholds, user interfaces, focusselectors, icons, and buttons described above with reference to method8200 optionally have one or more of the characteristics of the inputs,contacts, intensity thresholds, duration thresholds, user interfaces,focus selectors, icons, and buttons described herein with reference toother methods described herein (e.g., those listed in the fifthparagraph of the Description of Embodiments). For brevity, these detailsare not repeated here.

In accordance with some embodiments, FIG. 10 shows a functional blockdiagram of an electronic device 8300 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 10 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 10, electronic device 8300 includes display unit 8302configured to display a lower-level user interface that is part of auser interface hierarchy, where: the hierarchy includes at least threelevels, including the lower-level user interface, an intermediate-leveluser interface and a higher-level user interface; the intermediate-leveluser interface is above the lower-level user interface in the hierarchy;and the higher-level user interface is above both the intermediate-leveluser interface and the lower-level user interface in the hierarchy.Electronic device 8300 further includes touch-sensitive surface unit8304 configured to receive user inputs; one or more sensor units 8305configured to detect intensity of contacts with the touch-sensitivesurface unit; and a processing unit 8306 coupled to the display unit8302, the touch-sensitive surface unit 8304, and the sensor units 8305.In some embodiments, processing unit 8306 includes detecting unit 8308,replacing unit 8310, determining unit 8312, switching unit 8314, anddisplay enabling unit 8316.

Processing unit 8306 is configured to, while displaying the lower-leveluser interface, detect an input (e.g., with detecting unit 8308) on aportion of the device that is associated with user interface hierarchynavigation and, in response to detecting the input, in accordance with adetermination that the input has a duration shorter than a respectivetime threshold, replace (e.g., with replacing unit 8310) display of thelower-level user interface with display of the higher-level userinterface, and in accordance with a determination that the input has aduration longer than the respective time threshold, replace (e.g., withreplacing unit 8310) display of the lower-level user interface withdisplay of a respective user interface in the user interface hierarchyselected in accordance with an intensity of the input.

In some embodiments, the portion of the device on which the input isdetected (e.g., with detecting unit 8308) is a physical button.

In some embodiments, the portion of the device on which the input isdetected (e.g., with detecting unit 8308) is a portion of thetouch-sensitive surface unit that is associated with hierarchynavigation.

In some embodiments, the portion of the device on which the input isdetected (e.g., with detecting unit 8308) is a portion of a touch screendisplay unit that includes an icon associated with hierarchy navigation.

In some embodiments, the input is a contact on a touch-sensitive surfaceunit.

In some embodiments, the input includes a contact detected (e.g., withdetecting unit 8308) on the touch-sensitive surface unit and the inputis a stationary gesture that does not include lateral movement of thecontact on the touch-sensitive surface unit.

In some embodiments, the hierarchy includes exactly three levels inorder from highest to lowest: the higher-level user interface; theintermediate-level user interface; and the lower-level user interface.

In some embodiments, the higher-level user interface is adjacent to theintermediate-level user interface in the hierarchy and theintermediate-level user interface is adjacent to the lower-level userinterface in the hierarchy.

In some embodiments, the hierarchy includes more than three levels.

In some embodiments, the lower-level and intermediate-level userinterfaces are user interfaces in a single application and thehigher-level user interface is an application launch user interface.

In some embodiments, the lower-level, intermediate-level andhigher-level user interfaces are user interfaces in a singleapplication.

In some embodiments, the lower-level user interface is a mediapresentation interface, the intermediate-level user interface is a mediacollection display interface of a media player application, and thehigher-level user interface is an application launch user interface thatincludes an icon representing the media player application.

In some embodiments, the lower-level user interface is a subfolder, theintermediate-level user interface is a folder containing the subfolder,and the higher-level user interface is an application launch interfacethat includes an icon representing the folder.

In some embodiments, replacing (e.g., with replacing unit 8310) displayof the lower-level user interface with the higher-level user interfaceincludes enabling display of (e.g., with display enabling unit 8316) ananimated transition between the lower-level user interface and thehigher-level user interface where the animated transition progresses ata rate that corresponds to the intensity of the input.

In some embodiments, replacing (e.g., with replacing unit 8310) displayof the lower-level user interface with the higher-level user interfaceincludes enabling display of (e.g., with display enabling unit 8316) ananimated transition between the lower-level user interface and thehigher-level user interface where the animated transition progresses inaccordance with the intensity of the input.

In some embodiments, replacing (e.g., with replacing unit 8310) displayof the lower-level user interface with display of the respective userinterface selected in accordance with the intensity of the input, suchthat the respective user interface is the higher level user interface,includes enabling display of (e.g., with display enabling unit 8316) ananimated transition between the lower-level user interface and thehigher-level user interface that includes enabling display of arepresentation of the intermediate-level user interface.

In some embodiments, replacing (e.g., with replacing unit 8310) displayof the lower-level user interface with display of the respective userinterface selected in accordance with the intensity of the inputincludes, in accordance with a determination that the input has anintensity above a first intensity threshold and below a second intensitythreshold higher than the first intensity threshold, replacing (e.g.,with replacing unit 8310) display of the lower-level user interface withdisplay of the intermediate-level user interface, and, in accordancewith a determination that the input has an intensity above the secondintensity threshold, replacing (e.g., with replacing unit 8310) displayof the lower-level user interface with display of the higher-level userinterface.

In some embodiments, when the input has a duration longer than therespective time threshold, and replacing (e.g., with replacing unit8310) display of the lower-level user interface with display of arespective user interface includes replacing display (e.g., withreplacing unit 8310) of the lower-level user interface with thehigher-level user interface, the processing unit is further configuredto enable display of (e.g., with display enabling unit 8316) atransition between the lower-level user interface and the higher-leveluser interface that includes enabling display of (e.g., with displayenabling unit 8316) a representation of the intermediate-level userinterface.

In some embodiments, when the input has a duration longer than therespective time threshold and replacing (e.g., with replacing unit 8310)display of the lower-level user interface with display of a respectiveuser interface includes replacing (e.g., with replacing unit 8310)display of the lower-level user interface with the higher-level userinterface, the processing unit is further configured to enable displayof (e.g., with display enabling unit 8316) a transition between thelower-level user interface and the higher-level user interface that doesnot include enabling display of (e.g., with display enabling unit 8316)a representation of the intermediate-level user interface.

In some embodiments, when the input has a duration shorter than therespective time threshold, the processing unit further configured toenable display of (e.g., with display enabling unit 8316) a transitionbetween the lower-level user interface and the higher-level userinterface that does not include enabling display of (e.g., with displayenabling unit 8316) a representation of the intermediate-level userinterface.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 9A-9E are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.10. For example, detection operation 8220, replacing operation 8234,replacing operation 8236 and switching operation 8246 are, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

Gradually Displaying a User Interface on a Display

Many electronic devices display a graphical user interface on a displayin response to a user action (e.g., moving a mouse or pressing a powerbutton) subsequent to the display being in a low-power state (e.g.,sleep mode or an off state) where the graphical user interface is notdisplayed on the display. However the transition between the low-powerstate and displaying the graphical user interface can be jarring to theuser and/or unnecessarily consume power of the device when the user doesnot want the transition the device out of the low-power state. Theembodiments described below improve on these methods by graduallydisplaying the graphical user interface in response to detecting achange in a characteristic of the contact (e.g., an increase inintensity of the contact) while a display of the device is in alow-power mode. If the input meets display-activation criteria (e.g.,the contact exceeds a respective intensity threshold), the devicegradually displays a respective user interface on the display (e.g., therespective user interface slides onto the display from an edge of thedisplay) that was not displayed when the device was in the low-powermode. If the input fails to meet display-activation criteria, the devicemaintains the display in the low-power mode. Furthermore, in someembodiments, in response to detecting a reversal of the change in thecharacteristic of the contact (e.g., the intensity of the contactdecreases subsequent to increasing in intensity), the device graduallyceases displaying the respective user interface (e.g., the respectiveuser interface slides off of the display towards an edge of thedisplay). Gradually displaying the graphical user interface in responseto detecting the change in the characteristic of the contact provides anefficient and intuitive user interface that reduces the cognitive burdenon the user and enables the user to cancel display of the graphical userinterface if the user does not want to transition the device out of thelow-power state after viewing the first portion of the gradual displayof the user interface.

FIGS. 11A-11U illustrate exemplary user interfaces for graduallydisplaying a respective user interface on a display in accordance withsome embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIGS. 12A-12D. FIGS. 11B-11L and 11S-11U include intensity diagrams thatshow the current intensity of the contact on the touch-sensitive surfacerelative to a plurality of intensity thresholds including a gradualdisplay intensity threshold (e.g., “IT₁”) and a display confirmationintensity threshold (e.g., “IT_(L)”). In some embodiments, operationssimilar to those described below with reference to “IT₁” are performedwith reference to a different intensity threshold (e.g., “IT₀,” “IT_(L)”or “IT_(D)”).

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is a touch screen 112,and the touch-sensitive surface includes tactile output generators 167on the display (FIG. 1A). For convenience of explanation, theembodiments described with reference to FIGS. 11A-11U and 12A-12D willbe discussed with reference to portable multifunction device 100 withtouch screen 112; however, analogous operations are, optionally,performed on a device with a display 450 and a separate touch-sensitivesurface 451 in response to detecting the contacts described in FIGS.11A-11U on touch-sensitive surface 451 while displaying the userinterfaces shown in FIGS. 11A-11U on display 450.

FIG. 11A illustrates portable multifunction device 100 with a display(e.g., touch screen 112). In this example, touch screen 112 is in alow-power mode (e.g., off). FIG. 11A further illustrates menu button204. In some embodiments, menu button is touch-sensitive (e.g., acontact is detected on menu button 204 via capacitive sensing). In someembodiments, the menu button is pressure sensitive but nottouch-sensitive (e.g., a contact is detected on menu button 204 by anincrease in intensity of the contact via one or more sensors).

FIGS. 11B-11C illustrate detecting an input on a touch-sensitive surface(e.g., menu button 204) including detecting contact 15302 on menu button204 and detecting a change in a characteristic (e.g., intensity) ofcontact 15302 (e.g., an increase in intensity of contact 15302). In thisexample, in response to detecting the input (e.g., contact 15302 on menubutton 204) and in accordance with a determination that the input meetsdisplay-activation criteria (e.g., the intensity of contact 15302 isabove IT₁), the device 100 gradually displays a respective userinterface. FIGS. 11B-11C further illustrate user interface 400,including: a communication network signal indicator 402, a batterycharge indicator 406, current time and date 15304, and unlock image15306.

In some embodiments, the respective user interface is not the entireuser interface. For example, in some embodiments, one or more objects oruser interface portions are displayed even during low-power mode, whileother user interface portions (herein called the respective userinterface) are not displayed in the low-power mode and are graduallydisplayed in response to a user input and in accordance a determinationthat the input meets display-activation criteria.

FIGS. 11B-11C and 11F illustrate gradually displaying the respectiveuser interface 400 on touch screen 112 by sliding the current time anddate 15304 from a top edge of touch screen 112 towards the center oftouch screen 112 (e.g., current time and date 15304 moves from position15304-a in FIG. 11B through intermediate position 15304-b in FIG. 11C tofully displayed position 15304-d in FIG. 11F) and by sliding unlockimage 15306 from a bottom edge of touch screen 112 towards the center oftouch screen 112 (e.g., unlock image 15306 moves from position 15306-ain FIG. 11B through intermediate position 15306-b in FIG. 11C to fullydisplayed position 15306-d in FIG. 11F). FIGS. 11B-11C and 11F furtherillustrate the intensity of contact 15302 increasing from below IT_(L)in FIGS. 11B-11C to above IT_(L) in FIG. 11F.

FIGS. 11B-11E illustrate detecting a reversal of the change in thecharacteristic (e.g., the intensity) of the contact after at leastpartially displaying the respective user interface on the display (e.g.,current time and date 15304 and unlock image 15306 are partiallydisplayed on touch screen 112 in positions 15304-b and 15306-b,respectively, in FIG. 11C). In this example, the intensity of contact15302 increases between FIGS. 11B-11C; then, the intensity of contact15302 decreases between FIGS. 11C-11D (e.g., a reversal of the change inthe intensity of contact 15302). FIG. 11D-11E further illustrategradually ceasing to display the respective user interface in responseto detecting the reversal of the change in the characteristic (e.g., theintensity) of the contact. In this example, the device gradually ceasesto display the respective user interface 400 by sliding the current timeand date 15304 from position 15304-b in FIG. 11C towards the top edge oftouch screen 112 (e.g., through intermediate positions 15304-a in FIG.11D and 15304-c in FIG. 11E) and by sliding the unlock image 15306 fromposition 15306-b in FIG. 11C towards the bottom edge of touch screen 112(e.g., through intermediate positions 15306-a in FIG. 11D and 15306-c inFIG. 11E). FIGS. 11C-11E further illustrate reversing the gradualappearance of the respective user interface by gradually ceasing todisplay the respective user interface in accordance with a determinationthat the characteristic (e.g., the intensity of contact 15302) did notmeet or exceed a respective (display confirmation) threshold (e.g., theintensity of contact 15302 does not meet or exceed a displayconfirmation intensity threshold IT_(L) in FIGS. 11B-11E) prior todetecting the reversal of the change in the characteristic of thecontact (e.g., the decrease in the intensity of contact 15302 betweenFIGS. 11C-11D).

FIGS. 11B-11C and 11F-11H illustrate detecting a reversal of the changein the characteristic (e.g., the intensity) of the contact after atleast partially displaying the respective user interface on the display(e.g., in FIG. 11C current time and date 15304 and unlock image 15306are partially displayed on touch screen 112 in positions 15304-b and15306-b, respectively). In this example, the intensity of contact 15302increases between FIGS. 11B-11C and 11F (e.g., above IT_(L) in FIG.11F); then, the intensity of contact 15302 decreases between FIGS.11F-11G (e.g., below IT_(L) in FIG. 11G). FIGS. 11G-11H illustratemaintaining display of the respective user interface 400 (e.g., currenttime and date 15304 remains in position 15304-d and unlock image 15306remains in position 15306-d) in accordance with a determination that thecharacteristic (e.g., the intensity of contact 15302) met or exceededdisplay confirmation intensity threshold (e.g., the intensity of contact15302 exceeds IT_(L) in FIG. 11F) prior to detecting the reversal of thechange in the characteristic (e.g., the decrease in the intensity ofcontact 15302 between FIGS. 11F-11G).

FIGS. 11I-11L illustrate gradually displaying an additional portion ofthe respective user interface 400 (e.g., media controls 15308) bysliding media controls 15308 onto touch screen 112 from a bottom edge oftouch screen 112 in accordance with a change in the characteristic(e.g., an increase in intensity) of the contact (e.g., contact 15302)and in accordance with a determination that the characteristic (e.g.,the intensity of contact 15302) exceeds the display confirmationintensity threshold (e.g., “IT_(L)”). In this example, media controls15308 are gradually displayed on touch screen 112 by sliding mediacontrols 15308 from the bottom edge of touch screen 112 towards thecenter of touch screen 112 (e.g., media controls 15308 move fromposition 15308-a in FIG. 11I through intermediate positions 15308-b and15308-c in FIGS. 11J-11K, respectively, to fully displayed position15308-d in FIG. 11L). FIGS. 11I-11L further illustrate current time anddate 15304 and unlock image 15306 moving from fully displayed positions15304-d and 15306-d, respectively, in FIG. 11F towards the center oftouch screen to final positions 15304-h and 15306-h, respectively, inFIG. 11L, however in some embodiments, current time and date do not movewhen the additional portion of the respective user interface isdisplayed. In this example, media controls 15308 are fully displayed ontouch screen 112 in FIG. 11L in accordance with a determination that thecharacteristic (e.g., the intensity of contact 15302) exceeds a secondthreshold such as deep press intensity threshold (e.g., “IT_(D)”).

FIGS. 11M-11O illustrate gradually displaying the user interface 400(e.g., including current time and date 15304 and unlock image 15306) ontouch screen 112 in accordance with the change in a characteristic(e.g., a change in the position) of contact 15302 on touch screen 112.In this example, user interface 400 is gradually displayed in responseto detecting contact 15302 on touch screen 112 and in accordance with adetermination that contact 15302 meets display-activation criteria(e.g., contact 15302 on moves by more than a predefined amount orcontact 15302 moves from an edge of touch screen 112 in a predefineddirection by more than a predefined amount). In this example, userinterface 400 is gradually displayed in accordance with the change inthe position of contact 15310 (e.g., contact 15310 moves vertically fromposition 15310-a at the bottom edge of touch screen 112 in FIG. 11Mthrough intermediate position 15310-b in FIG. 11N to position 15310-c inFIG. 11O, a total movement distance of approximately 25% of alongitudinal distance of touch screen 112). FIGS. 11M-11O furtherillustrate gradually displaying user interface 400 by sliding currenttime and date 15304 from a top edge of touch screen 112 towards thecenter of touch screen 112 (e.g., current time and date 15304 moves fromposition 15304-a in FIG. 11M through intermediate position 15304-b inFIG. 11N to fully displayed position 15304-d in FIG. 11O) and unlockimage 15306 from a bottom edge of touch screen 112 towards the center oftouch screen 112 (e.g., unlock image 15306 moves from position 15306-ain FIG. 11M through intermediate position 15306-b in FIG. 11N to fullydisplayed position 15306-d in FIG. 11O).

FIGS. 11P-11Q illustrate gradually displaying an additional portion(e.g., media controls 15308) of the respective user interface 400 inresponse to detecting a second input on the touch screen (e.g., contact15312) subsequent to detecting a first user input (e.g., contact 15310in FIGS. 11M-11O) and in accordance with a change in the position ofcontact 15312 on touch screen 112 (e.g., contact 15312 moves fromposition 15312-a in FIG. 11P to position 15312-b in FIG. 11Q). In thisexample, the additional portion (e.g., media controls 15308) of therespective user interface 400 is gradually displayed in response todetecting contact 15312 on touch screen 112 and in accordance with adetermination that contact 15312 meets display-activation criteria(e.g., movement of contact 15312 on touch screen 112 by more than apredefined amount or movement of contact 15312 from an edge of touchscreen 112 in a predefined direction by more than a predefined amount).FIG. 11Q further illustrates media controls 15308 at fully displayedposition 15312-b on touch screen 112.

FIGS. 11R-11U illustrate gradually fading in respective user interface400 (e.g., including current time and date 15304 and image unlock 15304)on touch screen 112. In this example, the respective user interface 400gradually fades in on touch screen 112 in accordance with the intensityof contact 15314 (e.g., an increase in intensity of contact 15314between IT₁ to IT_(L)). FIG. 11U illustrates user interface 400 fullyfaded in on touch screen 112 in accordance with a determination that thecharacteristic (e.g., intensity) of contact 15314 meets or exceeds thedisplay confirmation intensity threshold (e.g., “IT_(L)”).

FIGS. 12A-12D are flow diagrams illustrating a method 15400 of graduallydisplaying a respective user interface on a display in accordance withsome embodiments. The method 15400 is performed at an electronic device(e.g., device 300, FIG. 3, or portable multifunction device 100, FIG.1A) with a display and a touch-sensitive surface. In some embodiments,the display is a touch screen display and the touch-sensitive surface ison the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 15400 are,optionally, combined and/or the order of some operations is, optionally,changed.

As described below, the method 15400 provides an intuitive way togradually display a respective user interface on a display, for examplewhile transitioning from a low-power mode. The method reduces thecognitive burden on a user when gradually displaying a respective userinterface on a display, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user togradually display a respective user interface on a display faster andmore efficiently conserves power and increases the time between batterycharges.

While a display is in a low-power mode (e.g., the backlight of thedisplay is off and/or the display is off), the device detects (15402) aninput on a touch-sensitive surface. FIG. 11A, for example, shows touchscreen 112 in the low-power mode. FIG. 11B, for example, shows an input(e.g., contact 15302) detected on a touch-sensitive surface (e.g.,button 204).

Detecting the input includes (15404) detecting a contact on thetouch-sensitive surface and detecting a change in a characteristic ofthe contact. FIGS. 11A-11B, for example, show the device detecting aninput including contact 15302 on menu button 204 and a change in acharacteristic (e.g., intensity) of contact 15302 (e.g., an increase inintensity of contact 15302).

In some embodiments, the change in the characteristic is (15406) achange in intensity of the contact. FIGS. 11B-11C, for example, show achange in the intensity of contact 15302 (e.g., an increase in intensityof contact 15302). In some embodiments, the change in the characteristicis (15408) a change in position of the contact on the touch-sensitivesurface (e.g., a vertical or horizontal component of movement of thecontact on the touch-sensitive surface starting from an edge of thedisplay). FIGS. 11M-11O, for example, show a change in position ofcontact 15310 on touch screen 112 (e.g., contact 15310 moves verticallystarting from position 15310-a in FIG. 11M at an edge of touch screen112 through intermediate position 15310-b in FIG. 11N to final position15310-c in FIG. 11O).

In response to detecting (15410) the input and in accordance with adetermination that the input meets (15412) the display-activationcriteria, the device gradually displays (15414) a respective userinterface on the display in accordance with the change in thecharacteristic of the contact, where the respective user interface wasnot displayed on the display when the display was in the low-power mode.In some embodiments, gradually displaying the respective user interfacein accordance with the change in the characteristic of the contactincludes determining a current display state of the respective userinterface (e.g., a display state parameter that varies between 0% and100%) based on a current value of the characteristic (e.g., where aplurality of values of the characteristic are mapped to correspondingvalues of the display state between 0% displayed and 100% displayed).

As noted above, in some embodiments, the respective user interface isnot the entire user interface. For example, in some embodiments, one ormore objects or user interface portions are displayed even duringlow-power mode, while other user interface portions (herein called therespective user interface) are not displayed in the low-power mode andare gradually displayed in response to a user input and in accordance adetermination that the input meets display-activation criteria.

In some embodiments, the value of the display state parametercorresponds to a brightness of a backlight of the display between alow-power mode and a normal-operation mode. In some embodiments, thevalue of the display state parameter corresponds to an amount of therespective user interface that has been translated onto the display. Asone example, a slow change in the characteristic will result in acorresponding slow transition (through a plurality of intermediatedisplay states) to displaying the respective user interface on thedisplay. As another example, a fast change in the characteristic willresult in a corresponding fast transition (through a plurality ofintermediate display states) to displaying the respective user interfaceon the display. In either of these examples, the respective userinterface is gradually displayed on the display by displaying aplurality of intermediate display states over time rather than simplyswitching from the respective user interface being “off” of the displayto the respective user interface being “on” the display.

FIGS. 11B-11C, for example, show gradually displaying a respective userinterface 400 (e.g., including current time and date 15304 and unlockimage 15306) on touch screen 112 that was not displayed on touch screen112 when the touch screen was in the low-power mode (e.g., touch screen112 is in the low-power mode in FIG. 11A) in accordance with the changein the characteristic (e.g., intensity) of the input (e.g., theintensity of contact 15302 increases between FIGS. 11B-11C). The devicegradually displays respective user interface 400 on touch screen 112,for example, in response to detecting the input (e.g., contact 15302 isdetected on home button 204 in FIGS. 11B-11C) and in accordance with adetermination that the input (e.g., contact 15302) meetsdisplay-activation criteria (e.g., the intensity of contact 15302 meetsor exceeds IT₁).

In some embodiments, gradually displaying the respective user interfaceincludes (15416) gradually increasing the brightness of the display(e.g., gradually increasing the brightness of a backlight of thedisplay). In some embodiments, gradually displaying the respective userinterface includes (15418) gradually fading in the user interface on thedisplay. FIGS. 11R-11U, for example, show the device 100 graduallydisplaying the respective user interface 400 (e.g., including currenttime and date 15304 and unlock image 15306) by fading in the userinterface 400 on touch screen 112. In some embodiments, graduallydisplaying the respective user interface includes (15420) sliding therespective user interface onto the display from an edge of the display.FIGS. 11B-11C and 11F, for example, show gradually displaying therespective user interface 400 (e.g., including current time and date15304 and unlock image 15306) by sliding the respective user interface500 onto touch screen 112 from an edge of touch screen 112 (e.g.,current time and date 15304 slides onto touch screen 112 from a top edgeof touch screen 112 into fully displayed position 15304-d in FIG. 11F,and unlock image 15306 slides onto touch screen 112 from a bottom edgeof touch screen 112 into fully displayed position 15306-d in FIG. 11F).

In some embodiments, gradually displaying the respective user interfaceincludes (15422) displaying an animation of the respective userinterface gradually appearing on the display, and the animationprogresses (15424) from a starting point to an ending point determinedbased on a current value of the characteristic. For example, a pluralityof speeds of progression through the animation are mapped tocorresponding intensity values of the contact in a range of detectableintensity values, or a plurality of speeds of progression through theanimation are mapped to corresponding distances of the contact from anedge of the display. FIGS. 11B-11C and 11F, for example, show the device100 displaying an animation of the respective user interface 400 (e.g.,including current time and date 15304 and unlock image 15306) graduallyappearing on touch screen 112 (e.g., the respective user interface 400slides onto touch screen 112 from an edge of touch screen 112). FIGS.11B-11C and 11F, for example, show the animation progressing from astarting point (e.g., current time and date 15304 partially displayed atposition 15304-a and unlock image 15306 partially displayed at position15306-a in FIG. 11B) to an ending point (e.g., current time and date15304 fully displayed at position 15304-d and unlock image 15306 fullydisplayed at position 15306-d in FIG. 11F) determined based on a currentvalue of the characteristic (e.g., the intensity of contact 15302).

In some embodiments, gradually displaying the respective user interfaceincludes (15422) displaying an animation of the respective userinterface gradually appearing on the display, and the animationprogresses (15426) from a starting point to an ending point inaccordance with a progression of the respective characteristic from afirst threshold (e.g., “IT₁”) to a second threshold (e.g., “IT_(L)”).For example, a plurality of stages of the animation are mapped tocorresponding intensity values of the contact in a range of detectableintensity values, or a plurality of stages of the animation are mappedto corresponding distances of the contact from an edge of the display.FIGS. 11B-11C and 11F, for example, show the device 100 displaying ananimation of the respective user interface 400 (e.g., including currenttime and date 15304 and unlock image 15306) gradually appearing on touchscreen 112 (e.g., the respective user interface 400 slides onto touchscreen 112 from an edge of touch screen 112). FIGS. 11B-11C and 11F, forexample, show the animation progressing from a starting point (e.g.,current time and date 15304 partially displayed at position 15304-a andunlock image 15306 partially displayed at position 15306-a in FIG. 11B)to an ending point (e.g., current time and date 15304 fully displayed atposition 15304-d and unlock image 15306 fully displayed at position15306-d in FIG. 11F) in accordance with a progression of the respectivecharacteristic (e.g., the intensity of contact 15302) from a gradualdisplay threshold (e.g., “IT₁”) to a display confirmation threshold(e.g., “IT_(L)”). In some embodiments, the progression is mapped to achange in position of a contact (e.g., change in position of contact15310 in FIGS. 11M-11O), where a first position on the touch-sensitivesurface (e.g., the position of contact 15310 proximate to an edge oftouch screen 112 in FIG. 11M) corresponds to the first threshold and asecond position on the touch-sensitive surface (e.g., the position ofcontact 15310 on touch screen 112 in FIG. 11O) corresponds to the secondthreshold.

In some embodiments, the respective user interface (e.g., an unlockscreen) includes (15428) one or more of: media player controls, cameracontrols, a current time, a current date, a communication network signalindicator, a background image, a battery charge indicator, a deviceevent notification, and an unlock image. FIG. 11L, for example, showsrespective user interface 400 including a communication network signalindicator 402, a battery charge indicator 406, current time and date15304, unlock image 15306 and media controls 15308 on touch screen 112.

In some embodiments, the display-activation criteria are met (15430)when the contact has an intensity above a respective intensitythreshold. FIG. 11B, for example, shows the intensity of contact 15302above the gradual display intensity threshold (e.g., “IT₁”). In someembodiments, the display-activation criteria are met (15432) when thecontact moves on the display (e.g., in a predefined direction) by morethan a predefined amount. FIGS. 11M-11O, for example, show contact 15310moving on touch screen 112 by more than a predefined amount (e.g.,contact 15310 moves from position 15310-a in FIG. 11M to position15310-c in FIG. 11O). In some embodiments, the display-activationcriteria are met (15434) when the contact moves from an edge of thedisplay in a predefined direction by more than a predefined amount.FIGS. 11M-11O, for example, show contact 15310 moving from an edge oftouch screen 112 (e.g., from position 15310-a at the bottom edge oftouch screen 112 in FIG. 11M) in a predefined direction (e.g., contact15310 moves vertically between FIGS. 11M-11O) by more than a predefinedamount (e.g., 25% of a longitudinal distance of touch screen 112 betweenFIGS. 11M-11O).

In some embodiments, while the display is in the low-power state, inaccordance with a determination that the input does not meet thedisplay-activation criteria, the device maintains (15436) the display inthe low-power state after detecting the input. For example, if anaccidental contact is detected on the display (e.g., a contact with anintensity below a respective intensity threshold or a contact thatstarts in the middle of the touch-sensitive surface rather than at anedge of the touch-sensitive surface), the display does not wake up;however, if a contact meets the display-activation criteria, the displayslowly wakes up, gradually displaying the respective user interface. Insome embodiments, in accordance with a determination that a second inputdoes not meet the display-activation criteria, the device maintains thedisplay in the low-power mode after detecting the second input. FIG.11R, for example, shows the device maintaining touch screen 112 in thelow-power state (e.g., off) after detecting an input (e.g., contact15314) in accordance with a determination that contact 15314 does notmeet the display-activation criteria (e.g., an intensity above thegradual display intensity threshold—IT₁).

In some embodiments, after at least partially displaying the respectiveinterface on the display, the device detects (15438) a reversal of thechange in the characteristic of the contact. FIGS. 11B-11C, for example,show the device detecting a change in the characteristic (e.g.,intensity) of contact 15302 (e.g., the intensity of contact 15302increases) and partially displaying the respective user interface 400(e.g., including current time and date 15304 and unlock image 15306) ontouch screen 112. Subsequently, FIGS. 11C-11D, for example, show thedevice detecting a reversal in the change of the characteristic (e.g.,intensity) of contact 15302 (e.g., the intensity of contact 15302decreases).

In some embodiments, in response to detecting (15440) the reversal ofthe change in the characteristic of the contact, the device graduallyceases (15442) to display the respective user interface. FIGS. 11D-11E,for example, show the device 100 gradually ceasing to display therespective user 400 (e.g., including current time and date 15304 andunlock image 15306) on touch screen 112 (e.g., current time and date15304 moves from position 15304-b in FIG. 11C to position 15304-c inFIG. 11E, and unlock image 15306 moves from position 15306-b in FIG. 11Cto position 15306-c in FIG. 11E) in response to detecting the reversalof the change in the characteristic (e.g., intensity) of contact 15302(e.g., the intensity of contact 15302 decreases between FIGS. 11C-11D).

In some embodiments, in response to detecting (15440) the reversal ofthe change in the characteristic of the contact and in accordance with adetermination that the characteristic met or exceeded a respectivethreshold (e.g., a display confirmation threshold) prior to detectingthe reversal of the change in the characteristic of the contact, thedevice maintains (15444) display of the respective user interface. FIGS.11G-11H, for example, show the device 100 maintaining display of therespective user interface 400 (e.g., current time and date 15304 andunlock image 15306 are maintained at positions 15304-d and 15306-d,respectively) in response to detecting the reversal of the change in thecharacteristic (e.g., intensity) of contact 15302 (e.g., the intensityof contact 15302 decreases between FIGS. 11F-11G) and in accordance witha determination that the intensity of contact 15302 met or exceeded adisplay confirmation intensity threshold (e.g., “IT_(L)”) prior todetecting the reversal of the change in the intensity of contact 15302(e.g., the intensity of contact 15302 exceeds IT_(L) in FIG. 11F).

In some embodiments, in response to detecting (15440) the reversal ofthe change in the characteristic of the contact and in accordance with adetermination that the characteristic did not meet or exceed therespective threshold (e.g., a display confirmation threshold) prior todetecting the reversal of the change in the characteristic of thecontact, the device reverses (15446) the gradual appearance of therespective user interface by gradually ceasing to display the respectiveuser interface (e.g., gradually dimming the display backlight, orsliding the user interface off of the display). FIGS. 11B-11E, forexample, show the device 100 reversing the gradual appearance of therespective user 400 (e.g., including current time and date 15304 andunlock image 15306) on touch screen 112 (e.g., current time and date15304 moves from position 15304-b in FIG. 11C to position 15304-c inFIG. 11E, and unlock image 15306 moves from position 15306-b in FIG. 11Cto position 15306-c in FIG. 11E) in response to detecting the reversalof the change in the characteristic (e.g., intensity) of contact 15302(e.g., the intensity of contact 15302 decreases between FIGS. 11C-11D)and in accordance with a determination that the intensity of contact15302 did not meet or exceed a display confirmation intensity threshold(e.g., “IT_(L)”) prior to detecting the reversal of the change in theintensity of contact 15302 (e.g., the intensity of contact 15302 doesnot exceed IT_(L) in FIGS. 11B-11E).

It should be understood that the particular order in which theoperations in FIGS. 12A-12D have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 15400 describedabove with respect to FIGS. 12A-12D. For example, the contacts,intensity thresholds and animations described above with reference tomethod 15400 optionally have one or more of the characteristics of thecontacts, intensity thresholds and animations described herein withreference to other methods described herein (e.g., those listed in thefifth paragraph of the Description of Embodiments). For brevity, thesedetails are not repeated here.

In accordance with some embodiments, FIG. 13 shows a functional blockdiagram of an electronic device 15500 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 13 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 13, an electronic device 15500 includes a display unit15502 configured to display information; a touch-sensitive surface unit15504 configured to receive contacts; one or more sensor units 15506configured to detect intensity of contacts with the touch-sensitivesurface unit 15504; and a processing unit 15508 coupled to the displayunit 15502, the touch-sensitive surface unit 15504 and the one or moresensor units 15506. In some embodiments, the processing unit 15508includes a detecting unit 15510, a determining unit 15512, a displayenabling unit 15514, a maintaining unit 15516, a ceasing unit 15518, anda reversing unit 15520. In some embodiments, a display control unitreplaces and is configured to perform the operations of the displayenabling unit 15514, the maintaining unit 15516, the ceasing unit 15518,and the reversing unit 15520.

The processing unit is configured to: while the display unit 15502 is ina low-power mode, detect (e.g., with the detecting unit 15510) an inputon the touch-sensitive surface unit 15504, wherein detecting the inputincludes detecting a contact on the touch-sensitive surface unit 15504and detecting a change in a characteristic of the contact. Theprocessing unit is further configured to: in response to detecting(e.g., with the detecting unit 15510) the input and in accordance with adetermination (e.g., with the determining unit 15512) that the inputmeets display-activation criteria, gradually display (e.g., with thedisplay enabling unit 15514) a respective user interface on the displayunit 15502 in accordance with the change in the characteristic of thecontact, wherein the respective user interface was not displayed on thedisplay unit 15502 when the display unit 15502 was in the low-powermode.

In some embodiments, the display-activation criteria are met when thecontact has an intensity above a respective intensity threshold. In someembodiments, the display-activation criteria are met when the contactmoves on the display unit 15502 by more than a predefined amount. Insome embodiments, the display-activation criteria are met when thecontact moves from an edge of the display unit 15502 in a predefineddirection by more than a predefined amount.

In some embodiments, the processing unit 15508 is further configured to,while the display unit 15502 is in the low-power state and in accordancewith a determination (e.g., with the determining unit 15512) that theinput does not meet the display-activation criteria, maintain (e.g.,with the maintaining unit 15516) the display unit 15502 in the low-powermode after detecting (e.g., with the detecting unit 15510) the input.

In some embodiments, the change in the characteristic of the contact isa change in intensity of the contact. In some embodiments, the change inthe characteristic of the contact is a change in position of the contacton the touch-sensitive surface unit 15504.

In some embodiments, the processing unit 15508 is further configured to,after at least partially displaying (e.g., with the display enablingunit 15514) the respective user interface on the display unit 15502:detect (e.g., with the detecting unit 15510) a reversal of the change inthe characteristic of the contact; and in response to detecting thereversal of the change in the characteristic of the contact, graduallycease (e.g., with the ceasing unit 15518) to display the respective userinterface.

In some embodiments, the processing unit 15508 is further configured to,after at least partially displaying (e.g., with the display enablingunit 15514) the respective user interface on the display unit 15502:detect (e.g., with the detecting unit 15510) a reversal of the change inthe characteristic of the contact; and in response to detecting thereversal of the change in the characteristic of the contact: inaccordance with a determination (e.g., with the determining unit 15512)that the characteristic met or exceeded a respective threshold prior todetecting the reversal of the change in the characteristic of thecontact, maintain (e.g., with the maintaining unit 15516) display of therespective user interface; and in accordance with a determination (e.g.,with the determining unit 15512) that the characteristic did not meet orexceed the respective threshold prior to detecting the reversal of thechange in the characteristic of the contact, reverse (e.g., with thereversing unit 15520) the gradual appearance of the respective userinterface by gradually ceasing (e.g., with the ceasing unit 15518) todisplay the respective user interface.

In some embodiments, gradually displaying (e.g., with the displayenabling unit 15514) the respective user interface includes graduallyincreasing the brightness of the display unit 15502. In someembodiments, gradually displaying (e.g., with the display enabling unit15514) the respective user interface includes gradually fading in theuser interface on the display unit 15502. In some embodiments, graduallydisplaying (e.g., with the display enabling unit 15514) the respectiveuser interface includes sliding the respective user interface onto thedisplay from an edge of the display unit 15502.

In some embodiments, gradually displaying (e.g., with the displayenabling unit 15514) the respective user interface includes displayingan animation of the respective user interface gradually appearing on thedisplay unit 15502; and the animation progresses from a starting pointto an ending point at a rate determined based on a current value of thecharacteristic.

In some embodiments, gradually displaying (e.g., with the displayenabling unit 15514) the respective user interface includes displayingan animation of the respective user interface gradually appearing on thedisplay unit 15502; and the animation progresses from a starting pointto an ending point in accordance with a progression of the respectivecharacteristic from a first threshold to a second threshold.

In some embodiments, the respective user interface includes one or moreof: media player controls, camera controls, a current time, a currentdate, a communication network signal indicator, a background image, abattery charge indicator, a device event notification, and an unlockimage.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 12A-12D are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.13. For example, detecting operation 15404, determining operation 15412,displaying operation 15420, maintaining operation 15436, and ceasingoperation 15442 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch screen 112, and event dispatcher module174 delivers the event information to application 136-1. A respectiveevent recognizer 180 of application 136-1 compares the event informationto respective event definitions 186, and determines whether a firstcontact at a first location on the touch-sensitive surface correspondsto a predefined event or sub-event, such as selection of an object on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190optionally utilizes or calls data updater 176 or object updater 177 toupdate the application internal state 192. In some embodiments, eventhandler 190 accesses a respective GUI updater 178 to update what isdisplayed by the application. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B

It should be understood that the particular order in which theoperations have been described above is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that the various processes separatelydescribed herein (e.g., those listed in the fifth paragraph of theDescription of Embodiments) can be combined with each other in differentarrangements. For example, the contacts, user interface objects, tactilesensations, intensity thresholds, and/or focus selectors described abovewith reference to any one of the various processes separately describedherein (e.g., those listed in the fifth paragraph of the Description ofEmbodiments) optionally have one or more of the characteristics of thecontacts, gestures, user interface objects, tactile sensations,intensity thresholds, and focus selectors described herein withreference to one or more of the other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments).For brevity, all of the various possible combinations are notspecifically enumerated here, but it should be understood that theclaims described above may be combined in any way that is not precludedby mutually exclusive claim features.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the various described embodiments to the precise forms disclosed.Many modifications and variations are possible in view of the aboveteachings. The embodiments were chosen and described in order to bestexplain the principles of the various described embodiments and theirpractical applications, to thereby enable others skilled in the art tobest utilize the various described embodiments with variousmodifications as are suited to the particular use contemplated.

What is claimed is:
 1. A non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by an electronic device with adisplay, a touch-sensitive surface and one or more sensors to detectintensities of contacts with the touch-sensitive surface, cause thedevice to: display, on the display, a lower-level user interface that ispart of a user interface hierarchy, wherein: the hierarchy includes atleast three separately displayed levels, including the lower-level userinterface, an intermediate-level user interface and a higher-level userinterface; the intermediate-level user interface is above thelower-level user interface in the hierarchy; the higher-level userinterface is above both the intermediate-level user interface and thelower-level user interface in the hierarchy; and the lower-level userinterface is displayed without displaying the intermediate-level userinterface and without displaying the higher-level user interface; whiledisplaying the lower-level user interface, detect an input on a portionof the device that is associated with user interface hierarchynavigation; and, in response to detecting the input: in accordance witha determination that the input meets first transition criteria thatinclude a criterion that a maximum intensity of the input is above afirst intensity threshold and below a second intensity threshold,wherein the first intensity threshold is above a nominalcontact-detection intensity threshold, wherein the second intensitythreshold is higher than the first intensity threshold: replace displayof the lower-level user interface with display of the intermediate-leveluser interface, including displaying a first animated transition inwhich a visual property of the lower-level user interface is graduallychanged as the intensity of the input increases to reveal theintermediate-level user interface; and cease to display the lower-leveluser interface; and in accordance with a determination that the inputmeets second transition criteria that include a criterion that a maximumintensity of the input is above the second intensity threshold, replacedisplay of the lower-level user interface with display of thehigher-level user interface, wherein the higher-level user interface isdisplayed without displaying the lower-level user interface and withoutdisplaying the intermediate-level user interface.
 2. The computerreadable storage medium of claim 1, wherein the portion of the device onwhich the input is detected is a portion of the touch-sensitive surfacethat is associated with hierarchy navigation.
 3. The computer readablestorage medium of claim 1, wherein: the input includes a contactdetected on a touch-sensitive surface; and the input is a stationarygesture that does not include lateral movement of the contact on thetouch-sensitive surface.
 4. The computer readable storage medium ofclaim 1, wherein: the lower-level and intermediate-level user interfacesare user interfaces in a single application; and the higher-level userinterface is an application launch user interface.
 5. The computerreadable storage medium of claim 1, wherein: the lower-level userinterface is a media presentation interface; the intermediate-level userinterface is a media collection display interface of a media playerapplication; and the higher-level user interface is an applicationlaunch user interface that includes an icon representing the mediaplayer application.
 6. The computer readable storage medium of claim 1,wherein replacing display of the lower-level user interface with thehigher-level user interface includes displaying a second animatedtransition between the lower-level user interface and the higher-leveluser interface where the second animated transition progresses at a ratethat corresponds to the intensity of the input.
 7. The computer readablestorage medium of claim 1, wherein replacing display of the lower-leveluser interface with the higher-level user interface includes displayinga second animated transition between the lower-level user interface andthe higher-level user interface where the second animated transitionprogresses in accordance with the intensity of the input.
 8. Thecomputer readable storage medium of claim 1, wherein replacing displayof the lower-level user interface with the higher-level user interfaceincludes displaying an animated transition between the lower-level userinterface and the higher-level user interface that includes displaying arepresentation of the intermediate-level user interface.
 9. The computerreadable storage medium of claim 1, wherein: the computer readablestorage medium includes instructions which cause the device to determinewhether the input has a duration longer than a respective timethreshold; and replacing display of the lower-level user interface withdisplay of the higher-level user interface includes: in accordance witha determination that the input has a duration longer than the respectivetime threshold, switch from displaying the lower-level user interface todisplaying a representation of the intermediate-level user interface andthen to displaying the higher-level user interface; and in accordancewith a determination that the input has a duration shorter than therespective time threshold, replace display of the lower-level userinterface with display of the higher-level user interface withoutdisplaying a representation the intermediate-level user interface. 10.An electronic device, comprising: a display; a touch-sensitive surface;one or more sensors to detect intensities of contacts with thetouch-sensitive surface; one or more processors; memory; and one or moreprograms, wherein the one or more programs are stored in the memory andconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: displaying, on the display, alower-level user interface that is part of a user interface hierarchy,wherein: the hierarchy includes at least three separately displayedlevels, including the lower-level user interface, an intermediate-leveluser interface and a higher-level user interface; the intermediate-leveluser interface is above the lower-level user interface in the hierarchy;the higher-level user interface is above both the intermediate-leveluser interface and the lower-level user interface in the hierarchy; andthe lower-level user interface is displayed without displaying theintermediate-level user interface and without displaying thehigher-level user interface; while displaying the lower-level userinterface, detecting an input on a portion of the device that isassociated with user interface hierarchy navigation; in response todetecting the input: in accordance with a determination that the inputmeets first transition criteria that include a criterion that a maximumintensity of the input is above a first intensity threshold and below asecond intensity threshold, wherein the first intensity threshold isabove a nominal contact-detection intensity threshold, wherein thesecond intensity threshold is higher than the first intensity threshold:replacing display of the lower-level user interface with display of theintermediate-level user interface, including displaying a first animatedtransition in which a visual property of the lower-level user interfaceis gradually changed as the intensity of the input increases to revealthe intermediate-level user interface; and ceasing to display thelower-level user interface; and in accordance with a determination thatthe input meets second transition criteria that include a criterion thata maximum intensity of the input is above the second intensitythreshold, replacing display of the lower-level user interface withdisplay of the higher-level user interface, wherein the higher-leveluser interface is displayed without displaying the lower-level userinterface and without displaying the intermediate-level user interface.11. The electronic device of claim 10, wherein the portion of the deviceon which the input is detected is a portion of the touch-sensitivesurface that is associated with hierarchy navigation.
 12. The electronicdevice of claim 10, wherein: the input includes a contact detected on atouch-sensitive surface; and the input is a stationary gesture that doesnot include lateral movement of the contact on the touch-sensitivesurface.
 13. The electronic device of claim 10, wherein: the lower-leveland intermediate-level user interfaces are user interfaces in a singleapplication; and the higher-level user interface is an applicationlaunch user interface.
 14. The electronic device of claim 10, wherein:the lower-level user interface is a media presentation interface; theintermediate-level user interface is a media collection displayinterface of a media player application; and the higher-level userinterface is an application launch user interface that includes an iconrepresenting the media player application.
 15. The electronic device ofclaim 10, wherein replacing display of the lower-level user interfacewith the higher-level user interface includes displaying a secondanimated transition between the lower-level user interface and thehigher-level user interface where the second animated transitionprogresses at a rate that corresponds to the intensity of the input. 16.The electronic device of claim 10, wherein replacing display of thelower-level user interface with the higher-level user interface includesdisplaying a second animated transition between the lower-level userinterface and the higher-level user interface where the second animatedtransition progresses in accordance with the intensity of the input. 17.The electronic device of claim 10, wherein replacing display of thelower-level user interface with the higher-level user interface includesdisplaying an animated transition between the lower-level user interfaceand the higher-level user interface that includes displaying arepresentation of the intermediate-level user interface.
 18. Theelectronic device of claim 10, wherein: the electronic device includesinstructions for determining whether the input has a duration longerthan a respective time threshold; and replacing display of thelower-level user interface with display of the higher-level userinterface includes: in accordance with a determination that the inputhas a duration longer than the respective time threshold, switch fromdisplaying the lower-level user interface to displaying a representationof the intermediate-level user interface and then to displaying thehigher-level user interface; and in accordance with a determination thatthe input has a duration shorter than the respective time threshold,replace display of the lower-level user interface with display of thehigher-level user interface without displaying a representation theintermediate-level user interface.
 19. A method, comprising: at anelectronic device with a touch-sensitive surface and a display, whereinthe device includes one or more sensors to detect intensities ofcontacts with the touch-sensitive surface: displaying, on the display, alower-level user interface that is part of a user interface hierarchy,wherein: the hierarchy includes at least three separately displayedlevels, including the lower-level user interface, an intermediate-leveluser interface and a higher-level user interface; the intermediate-leveluser interface is above the lower-level user interface in the hierarchy;the higher-level user interface is above both the intermediate-leveluser interface and the lower-level user interface in the hierarchy; andthe lower-level user interface is displayed without displaying theintermediate-level user interface and without displaying thehigher-level user interface; while displaying the lower-level userinterface, detecting an input on a portion of the device that isassociated with user interface hierarchy navigation; in response todetecting the input: in accordance with a determination that the inputmeets first transition criteria that include a criterion that a maximumintensity of the input is above a first intensity threshold and below asecond intensity threshold, wherein the first intensity threshold isabove a nominal contact-detection intensity threshold, wherein thesecond intensity threshold is higher than the first intensity threshold;replacing display of the lower-level user interface with display of theintermediate-level user interface, including displaying a first animatedtransition in which a visual property of the lower-level user interfaceis gradually changed as the intensity of the input increases to revealthe intermediate-level user interface; and ceasing to display thelower-level user interface; and in accordance with a determination thatthe input meets second transition criteria that include a criterion thata maximum intensity of the input is above the second intensitythreshold, replacing display of the lower-level user interface withdisplay of the higher-level user interface, wherein the higher-leveluser interface is displayed without displaying the lower-level userinterface and without displaying the intermediate-level user interface.20. The method of claim 19, wherein the portion of the device on whichthe input is detected is a portion of the touch-sensitive surface thatis associated with hierarchy navigation.
 21. The method of claim 19,wherein: the input includes a contact detected on a touch-sensitivesurface; and the input is a stationary gesture that does not includelateral movement of the contact on the touch-sensitive surface.
 22. Themethod of claim 19, wherein: the lower-level and intermediate-level userinterfaces are user interfaces in a single application; and thehigher-level user interface is an application launch user interface. 23.The method of claim 19, wherein: the lower-level user interface is amedia presentation interface; the intermediate-level user interface is amedia collection display interface of a media player application; andthe higher-level user interface is an application launch user interfacethat includes an icon representing the media player application.
 24. Themethod of claim 19, wherein replacing display of the lower-level userinterface with the higher-level user interface includes displaying asecond animated transition between the lower-level user interface andthe higher-level user interface where the second animated transitionprogresses at a rate that corresponds to the intensity of the input. 25.The method of claim 19, wherein replacing display of the lower-leveluser interface with the higher-level user interface includes displayinga second animated transition between the lower-level user interface andthe higher-level user interface where the second animated transitionprogresses in accordance with the intensity of the input.
 26. The methodof claim 19, wherein replacing display of the lower-level user interfacewith the higher-level user interface includes displaying an animatedtransition between the lower-level user interface and the higher-leveluser interface that includes displaying a representation of theintermediate-level user interface.
 27. The method of claim 19, wherein:the method includes determining whether the input has a duration longerthan a respective time threshold; and replacing display of thelower-level user interface with display of the higher-level userinterface includes: in accordance with a determination that the inputhas a duration longer than the respective time threshold, switch fromdisplaying the lower-level user interface to displaying a representationof the intermediate-level user interface and then to displaying thehigher-level user interface; and in accordance with a determination thatthe input has a duration shorter than the respective time threshold,replace display of the lower-level user interface with display of thehigher-level user interface without displaying a representation theintermediate-level user interface.